Sandbox and environments

Fleet has one API host, https://api.get-fleet.com/v1, and the key decides the environment:

Key prefix	Environment	Acts on
flt_live_	Live	Your real organization’s data.
flt_test_	Test	A sandbox organization: a separate Fleet organization for building and testing.

The two never cross: a flt_test_ key is rejected for a real organization and a flt_live_ key for a sandbox, with invalid_api_key. Request logs record which environment each call used.

Sandbox organizations

Opening in the next release

Sandbox organizations open with the next release of the developer platform. Until then, start with a read-only live key: reads have no side effects, so you can build and test your sync logic safely, then add write scopes once you are ready.

A sandbox is an ordinary Fleet organization flagged as a sandbox. You can sign in to it in the Fleet app and see everything your integration creates there. In a sandbox:

• No one is notified. SMS, email, Slack, push notifications and Odoo pushes are switched off.
• Nothing is billed, and data is not counted towards plan limits.
• Everything else, including validation, permissions, rate limits and response shapes, behaves exactly as in live.

You create flt_test_ keys in the sandbox’s Settings → Developers, exactly as you create live keys.

What ships with sandboxes

• Self-serve sandboxes from this site, with realistic sample data (vehicles, drivers, fuel, inspections).
• Reset to restore the sample data.
• Simulators that trigger events such as a failed inspection or an overdue service, so you can test how your integration reacts.

See the changelog for progress.