Test mode is a complete copy of the Partner API that never touches real devices, real payment methods or real customers. Use it to build and to run your automated tests.
- Test keys (
fpk_test_…,ftk_test_…) only see test data; live keys only see live data. The portal has a Live/Test switch; forms opened in one mode are refused in the other (TEST_MODE_MISMATCH). - Activations, deactivations and fleet provisioning run against a simulator and complete within seconds. Nothing is billed; test statements and invoices are labelled Simulated.
- Emails caused by test actions go only to the person who acted, with a
[TEST]subject. - Webhooks: test-mode events go only to test-mode endpoints, signed exactly like live ones.
- The Tracking API returns deterministic simulated positions and journeys (
"simulated": true).
Magic identifiers
Register test devices with an IMEI ending in one of these digits to exercise failure handling:
| IMEI ends with | What happens | What your integration should do |
|---|---|---|
0001 | Activation fails permanently (service.activation_failed, operation failed). | Show the failure, do not retry automatically. |
0002 | The tracking platform applies the change but the first response is lost; Fleetalyse reconciles and completes the operation. | Keep polling or wait for the webhook — never re-request. |
0003 | The platform is slow; the operation is retried and completes later. | Tolerate operations that take minutes. |
Any other valid IMEI (15 digits passing the Luhn check, or 14 digits) activates normally.
Going live
Create live keys, register a live webhook endpoint and send its test event, then repeat one real activation and deactivation with a pilot device. Work through the Integration checklist.