Setup
1
Get your signing secret
doola provisions your tenant and generates your webhook signing secret. It is shown once at creation, so store it securely. Email engineering@doola.com to get set up or to rotate it.
2
Configure your endpoint
Set your webhook URL in the doola Partner Portal. The URL must be HTTPS. Each environment has its own tenant, so configure sandbox and production separately.
Verifying the signature
doola sends aPOST with an X-Doola-Signature header: an HMAC SHA256 hex digest of the raw request body, keyed with your webhook secret. (HTTP header names are case-insensitive; many frameworks lowercase them to x-doola-signature on the way in.)
Payload
Every delivery is aPOST with the same envelope. Only eventPayload changes shape from event to event.
Events
You may occasionally receive duplicate
document_* events for the same document, for example after doola re-issues a document. Handle uploads idempotently using documentId.The three SS-4 events fire only for non-US founders, who must sign an SS-4 before the IRS issues the EIN. The three
form8821 events mirror them and fire only for a non-US founder who also requested an expedited EIN, where a signed Form 8821 authorizes doola to retrieve the EIN letter from the IRS. In each pair, signature_*_completed fires the instant the founder signs; document_*_uploaded fires once the signed PDF is stored and downloadable. See Non-US founders for the full flow.company_ein_issued and document_einletter_uploaded both signal EIN issuance, at two distinct moments: company_ein_issued fires when doola records the EIN on the company (fetch the company to read the ein field), and document_einletter_uploaded fires once the IRS confirmation letter is stored and downloadable. They arrive independently, so do not assume an order. company_ein_issued fires only on the first issuance; a later correction to the EIN value does not re-fire it.The two governance-document events are entity-type specific:
document_corporatebylaws_uploaded fires for CCorp companies only, and document_operatingagreement_uploaded fires for LLC companies only. doola generates the governance document shortly after the Articles of Organization are processed, so each event typically arrives soon after document_aoo_uploaded.Example payloads
A sample delivery for every event. WithineventPayload, only the fields relevant to that event are present; inapplicable fields are omitted entirely rather than sent as null, so parse defensively. eventPayload itself is null only for partner_webhook_disabled.
company_formation_submitted
company_formation_submitted
company_formation_completed
company_formation_completed
company_formation_failed
company_formation_failed
company_filing_date_updated
company_filing_date_updated
company_ein_issued
company_ein_issued
document_aoo_uploaded
document_aoo_uploaded
document_einletter_uploaded
document_einletter_uploaded
document_mail_uploaded
document_mail_uploaded
document_corporatebylaws_uploaded
document_corporatebylaws_uploaded
document_operatingagreement_uploaded
document_operatingagreement_uploaded
signature_ss4_completed
signature_ss4_completed
document_ss4_uploaded
document_ss4_uploaded
signature_ss4_reminder_due
signature_ss4_reminder_due
signature_form8821_completed
signature_form8821_completed
document_form8821_uploaded
document_form8821_uploaded
signature_form8821_reminder_due
signature_form8821_reminder_due
partner_webhook_disabled
partner_webhook_disabled
Payload fields
doolaCompanyId is on every company- and document-scoped payload. The rest appear only on the events noted below:
Delivery and retries
If your endpoint does not return a2xx, doola retries up to 5 times: at 1 minute, 15 minutes, 1 hour, 12 hours, and 24 hours after the previous attempt. Treat every delivery as at least once.
After all retries fail, doola automatically disables your endpoint and sends a final partner_webhook_disabled event. Fix your endpoint and re-enable it in the Partner Portal. Re-enabling is a deliberate partner action, so you confirm the endpoint is healthy before traffic resumes.
Every delivery attempt (timestamp, event, HTTP status, attempt number) is visible in the Partner Portal.