> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Test mode

> Build and test against isolated test data and a simulated OEM. Your secret key selects the mode.

Test mode is an isolated environment in your account. Every endpoint works, and test data never mixes with live data.

The secret key sets the mode; the endpoints are the same, and every response carries `live_mode`.

| Mode | Secret key prefix | `live_mode` |
| :- | :- | :- |
| Test | `sk_test_` | `false` |
| Live | `sk_live_` | `true` |

Test mode is billed like live mode and has the same rate limits.

## Test OEM

Devices come from Connect; the API does not create them. In test mode, create the Connect session with the test OEM `oem_6a3a8dada72cd0a249ff9528`, which simulates an OEM and its devices.

Its storage devices declare location metering, so [list location meter records](/docs/fleet-api/reference/meter-records/list-location.md) returns records for their locations.

The [quickstart](/docs/fleet-api/guides/quickstart.md) runs the whole loop against the test OEM: create a program, connect a device, read its state, commit it to a VPP event and read the meter records.

## Test VPP events

Set `event_type` to `TEST` on a [VPP event](/docs/fleet-api/guides/dispatch/vpp-events.md) you create while testing. A `TEST` event runs the full dispatch chain and does not affect settlement.

## Events and webhooks

Every [event](/docs/fleet-api/guides/platform/events.md) carries `live_mode`, and test events are signed with a separate key, so one endpoint can take both modes. See [webhooks](/docs/fleet-api/guides/platform/webhooks.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.