Skip to content

Testing and access

~3 min · Resources

Getting a key

API keys are issued by DDS Wireless. Contact your representative or the Scheduled Routes API page to request one for evaluation or production. See Authentication for how to send it.

Testing safely

The API runs against production, so test deliberately:

  • Use a key issued to you, on an account/tenant meant for testing.
  • Start from the Quickstart hello-world payload, then swap in your own coordinates.
  • Don't send confidential or personal data you don't need to — use representative, non-sensitive test data.
  • Keep test volumes modest to stay within rate limits.

Trying it in the browser

The API reference has a Try it out console:

  1. Click Authorize, paste your key.
  2. Expand an endpoint → Try it out → edit the example → Execute.

Your key, your account

In-browser Try-it calls hit production using the key you paste, under your account. Never paste a key that isn't yours.

If Try-it fails with a network/CORS error

The browser console needs the API server to allow requests from this docs domain. If it fails, the copy-paste cURL/Python from the Quickstart still works. Report it to DDS Wireless so the docs origin can be allow-listed.

Related: Authentication · Quickstart · Rate limits and errors