Sandbox

The sandbox lets you exercise the full platform against realistic data without affecting production members or bookings — whether you use the SDK or call the API directly.

Routing to the sandbox

Any API key prefixed with pk_test_ is a sandbox key. Point your client at the sandbox endpoint and use that key:

GraphQL endpoint: https://staging-api.akintravel.com/graphql
API key: your pk_test_* key

On React, resolveConfig infers the right endpoints from the key prefix, so you don’t set URLs by hand:


import { resolveConfig } from '@akin-travel/partner-sdk';
 
const config = resolveConfig({ partnerId: 'your-partner-id', apiKey: 'pk_test_…' });
// → sandbox GraphQL + GIP endpoints

Off React, just send requests to the sandbox endpoint with your pk_test_* key.

Keys are environment-scoped. Each key is bound to one environment — a pk_test_* (sandbox) key only works against the sandbox endpoint, and a pk_live_* (production) key only against production. Sending a key to the wrong endpoint is rejected with HTTP 403 and a stable code of KEY_ENVIRONMENT_MISMATCH; the response body’s correctEndpoint names the URL that key targets. Don’t pattern-match the error message — branch on code.
{
  "error": "API key environment mismatch: this key is for the 'staging' environment, but this endpoint serves 'production'.",
  "code": "KEY_ENVIRONMENT_MISMATCH",
  "keyEnvironment": "staging",
  "apiEnvironment": "production",
  "correctEndpoint": "https://staging-api.akintravel.com/graphql"
}

Test members

Your onboarding contact seeds your sandbox with stable test members across the tier ladder and shares their sign-in details. Magic-link sign-in is wired so you can authenticate them without waiting on real email delivery.

We don’t publish fixed sandbox addresses here because they’re provisioned per partner — check your onboarding pack, or ask your AKIN Travel contact for the current set.

Test properties & bookings

A small set of partner-visible properties exists in the sandbox. The booking engine accepts arbitrary date ranges; nothing is committed to a real PMS.

Resetting state

Phase 1.4 — coming soon

A self-service reset that wipes the calling partner’s sandbox state (members, bookings, perks) and reseeds is on the roadmap. Until it ships, ask your AKIN Travel contact to reset.

Going live

When you’re ready to ship, swap the pk_test_* key for the matching pk_live_* key and point at the production endpoint (https://api.akintravel.com/graphql). With the SDK, resolveConfig switches automatically — no other code change.