Skip to main content
Onboarding turns your welcome kit into a live integration. Your onboarding contact can tell you, at any point, which step you are on and what is waiting on you.

​
The shape of onboarding

Onboarding is not a single fixed line of steps. It is:
  1. One setup step the platform runs first — your client and brand workspace is created.
  2. A group of steps that run in parallel. Once setup is done, several steps open at the same time. Some are yours to complete, some are ours, and some are with third parties. They do not run in a fixed order — each moves at its own pace, and finishing one never has to wait on another. The current group includes:
    • Yours: executing your agreements, setting up your login domain (a CNAME record you add), and granting payment-gateway access.
    • Ours: confirming the setup fee and billing mandate, mapping the intake questionnaires to your products, and provisioning your clinical-integration account.
    • Third-party: LegitScript certification, identity verification, and A2P (10DLC) phone approval.
  3. A go-live gate the platform runs last — a synthetic test order runs through your own workspace in test mode, you give your approval, and production is enabled.
Because the middle group runs concurrently, the number of steps reflects the live onboarding model rather than a fixed count — today it is around a dozen. Your onboarding contact reads the real total from the platform, so take the timeline from them, never from this page.

​
See what’s waiting on you

Read it yourself with your API key, using the onboarding id (onb_...) from your welcome kit:
$ONBOARDING_ID is your onb_... id; set X-Brand-Id to any one of your brands. The answer is the plain-language view the platform keeps for you: which step you are on out of how many, and the list of what is waiting on you. An empty list means the work is on our side. When your onboarding has a LegitScript step, the answer also lists each update’s date and what it means. You can read only your own onboarding. An id that belongs to another client answers 404, exactly as an id that does not exist. Your onboarding contact sees the same view, so you can also ask them and quote your onboarding id.