Differences between sandbox and production
The sandbox currently drives each vehicle at the speed below. A
fly profile keeps its own kmph.
The sandbox ignores a speed you send on a road profile. For example, a
car with speedCap: 30 still drives at 50 km/h.
Checklist before switching to production
- Confirm account-specific quotas (rate limit, max payload size, simultaneous-running-plans threshold) against the published defaults; contact customer.success@kardinal.ai if your account’s values differ from the defaults.
- Re-run your integration against production with real data volumes. If your production order/resource counts are meaningfully larger than what you tested in sandbox, re-check your
maxOptimizationDurationsizing — see Handling large volumes rather than assuming sandbox-derived durations still apply. If your code giveswait, or your own wait loop, a time limit, make it longer than the plan’s longest wait in production. That wait is the plan’smaxOptimizationDuration, plus the time the plan spends waiting and processing before the search starts. See The quality vs. computation time trade-off. When you omitmaxOptimizationDuration, production uses 15 minutes. When the time limit runs out,waitfails withKardinalTimeoutError, but the plan keeps running. Don’t submit the plan again. Read its state later instead. - Re-verify geocoding. The API does not geocode addresses (see Positions and geocoding); confirm the same geocoding provider and pipeline used in sandbox testing is wired up for production data before go-live.
- Rotate to your production API token everywhere, including any long-lived config or secrets manager entries — see the next section.
Managing your long-term API token per environment
Each agency has its own long-term API token, obtained via the Console, once per agency — not a separate username/password pair (see Authentication and API keys). For production:- Store the
sandboxandproductiontokens as separate secrets, scoped to their respective deployment environments, so a staging deploy can never accidentally authenticate against production (or vice versa). - Confirm which agency a given long-term token was issued for before debugging a request that behaves unexpectedly — a token always authenticates successfully against its own agency, so using the wrong one doesn’t fail: it silently succeeds against that agency’s data instead. Check the
agencyIdfield in the response to confirm which agency you actually hit. - With an SDK, the switch is only a different
KARDINAL_API_KEYvalue per environment — same host, same code.kardinal auth checkshows which agency the key in use belongs to. - Regenerating a token replaces the previous one for that agency — roll the new value out everywhere before discarding the old one (see Token lifetime).
See also
- Authentication and API keys — obtaining, rotating, and storing your long-term API token.
- Limits and quotas — rate limits, payload size, and SLA, and how to confirm the values for your account.
- Handling large volumes — sizing
maxOptimizationDurationand paginating for production-scale data.

