Production Onboarding
Use this checklist before calling Turnqey production APIs or launching a partner integration.
Required setup
| Item | Required |
|---|---|
| Signed commercial or partner approval | Yes |
| Production client ID and secret | Yes |
| Registered production IP ranges | Yes, where applicable |
| Technical owner contact | Yes |
| Support escalation contact | Yes |
| Redirect or callback URLs | Yes, when using account authorization |
| Reconnect UX | Yes |
| Error and retry handling | Yes |
| Data display review | Yes |
| Security review | As required by partner workflow |
Go-live checklist
Before launch, confirm:
- Token requests work from production infrastructure.
- IP allowlisting is complete where required.
- Authorization URLs include state and checksum.
- Client identifiers map cleanly to partner users, households, or estate records.
- Collection grouping works for multiple connected sources.
- Balance and transaction endpoints handle cached and refreshed data.
- 401, 403, 422, 429, and 5xx responses have tested handling.
- Reconnect-required cases show clear user instructions.
- Support teams know where collection IDs, account IDs, and logs appear.
Launch rules
- Keep client secrets server-side.
- Do not expose access tokens in frontend code.
- Do not promise trading, withdrawal, or transfer functionality.
- Do not skip sandbox validation before production launch.
Support
For integration support, contact: