Sandbox
Use the Turnqey sandbox to build and test against the Unified API with test data before you ask for production access. Sandbox access is free and needs no approval.
This page covers the Unified API at account.turnqey.xyz. The Morningstar / ByAllAccounts API has its own separate sandbox. See Authentication for that one.1. Create an account
Sign up at https://account.turnqey.xyz. Verify your email, then set your password. Every organization gets a sandbox environment and a production environment.
2. Mint a sandbox API key
In the portal, open API keys and mint a sandbox key. Sandbox keys start with tq_sk_test_. Production keys start with tq_sk_live_.
The full key is shown only once, when you mint it. Store it in a secret manager. If you lose it, revoke it and mint a new one.
3. Make your first call
Send the key as a Bearer token. /api/v1/ping checks that your key works:
curl -X POST https://account.turnqey.xyz/api/v1/ping \
-H "Authorization: Bearer tq_sk_test_YOUR_KEY"A working key returns 200:
{
"data": {
"ok": true,
"keyPrefix": "tq_sk_test_1a2b3c4d",
"environmentType": "sandbox",
"occurredAt": "2026-10-30T16:00:00.000Z"
}
}The response also carries keyId, environmentId and productIds. A 200 from /ping proves your key works. It does not check the services behind the API. Use GET /api/v1/status for that.
4. Explore the endpoints
The portal has an API Explorer under Products → Unified API. It lists every endpoint, shows which ones are live, and builds a ready-to-copy curl command with your key.
What is different in the sandbox
- Test data: Sandbox keys return sample data, not real customer data.
- Heavy endpoints are blocked: Endpoints that run heavy calculations (tax exports, fiduciary memos, Exequtor and Q-Sim) do not run on sandbox keys and return an error. Test those with a production key.
- Rate limit: 60 requests per minute per key. Over the limit you get
429with aRetry-Afterheader.
Errors
Errors use application/problem+json:
{
"type": "https://docs.turnqey.xyz/errors/tq-invalid-key",
"title": "Invalid key",
"status": 401,
"detail": "Invalid API key.",
"code": "TQ_INVALID_KEY"
}| Status | Code | Meaning |
|---|---|---|
| 401 | TQ_UNAUTHENTICATED | The Authorization: Bearer header is missing. |
| 401 | TQ_INVALID_KEY | The key is wrong, revoked, suspended or expired. |
| 403 | TQ_SCOPE_FORBIDDEN | The key does not cover this endpoint's product. |
| 403 | TQ_LIVE_NOT_APPROVED | A production key called a product that is not approved yet. |
| 429 | TQ_RATE_LIMITED | Too many requests. Wait for Retry-After seconds. |
Moving to production
- In the portal, open Products and request production access for each product you need. Turnqey reviews the request and emails you the decision.
- When a product is approved, mint a production key (
tq_sk_live_) for it. - Make one call to
/api/v1/pingwith the production key to confirm it works.
See Production Onboarding for the full checklist.
Support
For integration support, contact: