Developer Accounts and Workspaces
How teams sign in, create a workspace, request sandbox access, and move toward production.
Who signs in
Platform access is built for the people who run the integration day to day: developers, technical leads, security owners, and billing or compliance contacts.
Each organization can invite the right people into the workspace without collapsing docs, API access, billing, and customer review into one shared login.
Workspace flow
Create an account, request sandbox access, issue the first key, connect a webhook, and review usage from the same workspace.
The goal is simple: keep account access, approvals, reporting, and integration history easy to find from the start instead of hiding them behind email threads.
From sandbox to production
Approved organizations move from sandbox to production through consent review, billing setup, integration verification, and audit-ready checks.
The portal keeps those stages explicit so teams always know whether they are reading public docs, working in sandbox, or using production credentials.