Founder address needed

Indiana and Illinois reject a formation whose business or mailing address is the registered agent’s address. When you create a company in either state with provider: registeredAgent on either address entry, doola still accepts the request (201), raises FORMATION_FOUNDER_ADDRESS_REQUIRED on the company and holds the formation until you send the founder’s own address.

This is a transition period. A future release will reject such a request with 400 E_VALIDATION_FAILED and error.fields.addresses.code: E_ADDRESSES_INVALID, so send the founder’s address when you create the company.

You are told by the company_founder_address_required webhook. See Required actions for the payload, the status model, and how to read actions back.

Avoid the action entirely: for a company in IN or IL, send both address entries with provider: customer and the founder’s address when you create the company.

The flow

While the action is open the company stays at formationSubmissionStatus: PENDING: nothing is filed and company_formation_submitted is not sent. Signing an SS-4 or Form 8821 is not blocked, and a signature made before you send the address stays valid.

Sending the founder’s address

Use the resolution endpoint with actionCode: FORMATION_FOUNDER_ADDRESS_REQUIRED and an addresses array: exactly one business and one mailing entry, both with provider: customer and "country": "USA" (exactly that value). The address does not have to be in Indiana or Illinois.

curl https://api.test.doola.com/v1/partner/companies/{companyId}/required-actions/{requiredActionId}/resolution \
  -X POST \
  -H "Authorization: dk_test_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "actionCode": "FORMATION_FOUNDER_ADDRESS_REQUIRED",
    "addresses": [
      { "provider": "customer", "type": "business", "address": { "line1": "251 W 30th St", "city": "New York", "state": "NY", "postalCode": "10001", "country": "USA" } },
      { "provider": "customer", "type": "mailing",  "address": { "line1": "251 W 30th St", "city": "New York", "state": "NY", "postalCode": "10001", "country": "USA" } }
    ]
  }'

The response is the action, already resolved, with its full history. The endpoint takes no Idempotency-Key: a second call after the action closed returns 409 E_REQUIRED_ACTION_CLOSED, so after a timeout read the action back instead of retrying. Unlike name options there is no state step to wait for: the addresses replace the company’s business and mailing addresses at once, and the formation continues from where it was held.

Errors

A body that breaks the rules above answers 400 E_VALIDATION_FAILED with error.fields.addresses.code set to E_ADDRESSES_INVALID; the message names the rule that failed (a registeredAgent entry, an address outside the US, a missing type). The full error table lists the rest.

Get started

Core concepts

Reference

API reference

Help

Updates

The flow

Sending the founder’s address

Errors

​The flow

​Sending the founder’s address

​Errors

The flow

Sending the founder’s address

Errors