Onboarding checklist
- Request submitted by an active insurer member
- Central approval completed for the requested environment and abilities
- Environment and credential owner verified
- Credential issued once through the existing credential controls
- GET /api/v2/integration/context confirms the binding
- Synthetic vehicle registered or matched
- Synthetic assessment submitted with an idempotency key
- Result retrieved after polling the API request reference
- Official test report retrieved only after authorized finalization
- Production activation separately approved by Quick Assess
The first request
Keep the bearer token server-side. Send Accept: application/json, Authorization: Bearer {token}, Idempotency-Key for state changes and an optional X-Request-ID. Record only the returned API-* request reference and server request ID in support notes.
Separate sandbox and production
A sandbox token cannot be promoted. Production requires a separate approved integration and credential with its own environment binding, owner, verified email, password confirmation and fresh 2FA step-up.
