Sandbox Access
Request sandbox access, get test subjects, run the first lookup, and prove the integration path before production review starts.
Sandbox approval should feel like a real queue with clear blocking checks, not a hidden email process.
Expected usage belongs in the sandbox lane because it shapes both approval and later billing expectations.
The operator should be able to move directly into a real request detail view from the summary page.
Once approved, the workspace receives a sandbox key, example subjects, and the first set of reporting and webhook tools.
That keeps the cutover to production clean because the integration shape is already proven.
If any of those steps are missing, fix them in sandbox first instead of carrying that uncertainty into live traffic.
The sandbox page should show whether the team already has a live review in flight.
Missing billing or webhook declarations should be obvious before the request is opened.
The page should tell the team exactly what gets them to approved.
The sandbox lane exists to unlock the first safe key, not just a docs acknowledgement.
Testing payloads and example records should be part of the approval outcome.
Once approved, the next screen should be the first protected lookup flow.
Sandbox access starts after the workspace, organization, and first project exist. The request captures the use case, the expected lookup pattern, and the billing owner.
Once approved, the workspace receives a sandbox key, example subjects, and the first set of reporting and webhook tools.
Sandbox calls use the same request structure as production. Teams can validate consent fields, webhook signatures, retries, and audit history before real customer traffic ever arrives.
That keeps the cutover to production clean because the integration shape is already proven.
Before production review, finish one successful lookup, verify at least one webhook delivery, confirm billing visibility, and make sure the team can trace key usage and audit history.
If any of those steps are missing, fix them in sandbox first instead of carrying that uncertainty into live traffic.