Start here
Access credentials
Use an access token and prevent network retries from creating duplicate tasks.
Access token
Section titled “Access token”Unless stated otherwise, every endpoint requires:
Authorization: Bearer YOUR_TOKENYour integration contact issues the token. Store it only on a server and read it from a secret manager or environment variable. Never place it in browser code, Git, logs, or support tickets.
The API returns HTTP 401 when the token is missing, expired, or invalid.
Request deduplication key
Section titled “Request deduplication key”Task submission also requires:
Idempotency-Key: monitor-request-20260812-0001This value prevents a timeout or disconnected retry from creating the same batch twice:
- Retry the same submission: reuse the original value.
- Submit a new batch: generate a new value.
- Length:
8–160characters. - Never use one value for two different request bodies.
A business order identifier or UUID is a good choice. Persist it with the submission record in your system.
Troubleshooting requests
Section titled “Troubleshooting requests”Responses include X-Request-ID. When contacting support, provide that identifier, the request time, and the endpoint URL. Do not provide the access token or full prompt content.