Environments
Production and the development 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 |
| Development | https://draco.dev.pulsarml.com | Building and testing your integration |
Every example on this site uses the production URL. To call the development environment instead, swap the base URL and use your development API key:
curl --location 'https://draco.dev.pulsarml.com/v1/machines' \
--header 'Accept: application/json' \
--header 'x-api-key: <YOUR_DEVELOPMENT_API_KEY>'The development environment
Development is a sandbox for testing the API with your real factory data. Use it to build and try out your integration before you point it at production.
API keys
Each environment has its own API key. A production key does not work against development, and a development key does not work against production.
Getting a development API key
Development API keys are requested the same way as production ones: contact your Customer Success Manager (CSM) and they will send it to you.
Try it in the docs
Every endpoint's playground has a server selector. Pick https://draco.dev.pulsarml.com there and paste your development key in the Authorization field to send requests to the sandbox.