Skip to main content
The test environment is a complete copy of production. Use your test keys and the SDK talks to it automatically: the pk_test_ key loads the app from sdk.test.doola.com, and the dk_test_ key calls api.test.doola.com. Nothing is ever filed with a state or the IRS.

Run a formation end to end

1

Start as a new customer

Each customer forms one company, so every run needs a fresh one. Sign in to your app as a new user, or send a new email and externalCustomerId when you mint the session. Plus-addresses such as you+sdk42@yourcompany.com work well.
2

Fill in the wizard and submit

Use realistic but made-up details. Leave the responsible party’s SSN empty to see the signing flow for founders without one.
3

Pay

Take the payment with your provider’s test mode, then confirm it with your dk_test_ key, exactly as in production. Mount the SDK again: the founder’s dashboard opens, on the signing step if the responsible party gave no SSN.
4

Sign

Sign the SS-4 inside the SDK. The test signing pages carry a “DEMO” watermark, and nothing reaches the IRS.
5

Complete formation and EIN

Wait for company_formation_submitted, then use the sandbox playground to complete the formation and issue the EIN on demand. Each call fires the real webhooks, and the documents appear on the founder’s dashboard.
Confirm payment before you use the playground. Like production, the playground never forms an unpaid company. It refuses one that is still AWAITING_PAYMENT with 422 E_FORMATION_AWAITING_PAYMENT, and a cancelled one with 409 E_COMPANY_CANCELLED, and leaves it unchanged.

Scenarios worth testing

Signing in testing

With test keys, signing renders inside the SDK on any page, localhost included. See Signatures.
Last modified on November 12, 2026