Environments
Production and the staging sandbox, and when to use each.
The Pulsar Public API runs in two environments. They expose the same endpoints; only the base URL and the API key change.
| Environment | Base URL | Use it for |
|---|---|---|
| Production | https://draco.prod.pulsarml.com | Your live integration |
| Sandbox (staging) | https://draco.stage.pulsarml.com | Building and testing your integration |
Every example on this site uses the production URL. To call the sandbox instead, swap the base URL and use your sandbox API key:
curl --location 'https://draco.stage.pulsarml.com/v1/machines' \
--header 'Accept: application/json' \
--header 'x-api-key: <YOUR_SANDBOX_API_KEY>'The sandbox
The sandbox is Pulsar's staging environment: a copy of production with your real factory data, for testing the API. Use it to build and try out your integration before you point it at production.
Sandbox data is reset every week
The sandbox is rebuilt from production every week. Anything you create or change there, such as work orders, SKUs, operators or production logs, is deleted, and an id you saved may later point to a different record, or to none. Don't store sandbox ids for later: look records up again before you use them.
Because the sandbox holds a copy of your company's real production data, a sandbox key gives access to the same information as a production key. Store it, share it and rotate it with the same care.
API keys
Each environment has its own API key. A production key does not work against the sandbox, and a sandbox key does not work against production.
Getting a sandbox API key
Both kinds of key are created by a Super Admin in the Pulsar app, under Settings → Integrations: the page has a Production / Sandbox switch, and a key is created for the environment selected. See Authentication.
Try it in the docs
Every endpoint's playground has a server selector. Pick https://draco.stage.pulsarml.com there and paste your sandbox key in the Authorization field to send requests to the sandbox.