First Protected Lookup
The end-to-end quickstart for organization setup, sandbox key issuance, first lookup, webhook check, and dashboard confirmation.
The detail page should show whether the first protected lookup has already passed and which step comes next.
A first-lookup quickstart should stay tied to the webhook check that proves the integration is really alive.
Once the basics are proven, the page should point directly at the release lane.
The point is not only to get a 200 response. It is to prove that the consent scope, declared purpose, and audit trail are already behaving correctly.
That keeps the first hour grounded in real operations instead of only code samples.
This is what makes the onboarding path feel like a real platform workflow instead of a collection of disconnected docs.
{
"workspace": "ws_northstar_platform",
"project": "proj_sandbox_workforce_review",
"key_label": "hrs-sandbox-backend",
"lookup_state": "verified",
"webhook_check": "passed",
"next_step": "production_review"
}A quickstart detail page should connect the first lookup, webhook verification, and production handoff in one traceable workflow.
The quickstart should stay tied to the real project that owns the first request.
The key powering the first lookup should remain visible on the same detail screen.
Once the first request and webhook are stable, the detail lane should point directly into live review.
A good quickstart should show the exact sequence: create the workspace, create the project, issue the key, call the endpoint, inspect the response, and verify the audit entry.
The point is not only to get a 200 response. It is to prove that the consent scope, declared purpose, and audit trail are already behaving correctly.
Right after the first lookup, the quickstart should move into webhook signature verification and retry testing so the integration path is proven before any production review starts.
That keeps the first hour grounded in real operations instead of only code samples.
Once the first lookup and the first webhook are clean, the page should point directly into production review with the exact project and key context preserved.
This is what makes the onboarding path feel like a real platform workflow instead of a collection of disconnected docs.