Quickstarts
Go from empty account to the first successful HRS lookup, webhook signature check, and dashboard review with minimal setup friction.
Quickstarts should behave like real operator runbooks, not a loose collection of docs pages.
The quickstart lane should tell the operator how many verified launch paths already exist.
The page should make the immediate action obvious without sending the user back to the overview.
Once approved, the platform issues a project key, exposes test subjects, and enables reports, key usage, and playground calls inside the dashboard.
Then subscribe a webhook endpoint and confirm that signed events arrive with the same project, organization, and consent context you declared.
The production checklist focuses on consent scope, audit retention, webhook verification, retry handling, and internal access controls.
The quickstarts page should make the exact first implementation path obvious.
Teams should see whether sandbox approval is already cleared before they burn time on setup.
The full sequence should stay legible from the top quickstart surface.
The quickstart should move directly into the real project that owns the work.
The first key should stay tied to the quickstart rather than floating as a generic secret.
A good quickstart should already point toward the live review lane.
Create a developer account or sign in, attach it to an organization workspace, create the first sandbox project, declare the use case, and wait for sandbox approval.
Once approved, the platform issues a project key, exposes test subjects, and enables reports, key usage, and playground calls inside the dashboard.
Make one HRS lookup in the playground or from your server, review the returned consent metadata, and verify that your audit trail captured the request correctly.
Then subscribe a webhook endpoint and confirm that signed events arrive with the same project, organization, and consent context you declared.
Production access adds billing usage, expanded report controls, export jobs, and organization-level health summaries.
The production checklist focuses on consent scope, audit retention, webhook verification, retry handling, and internal access controls.