Errors & troubleshooting
Use the HTTP status and error code to understand what happened and decide what to do next.
Read an error response#
Connect API errors include a stable code, a readable message and a request_id for investigation.
{
"code": "token_expired",
"message": "Token has expired.",
"request_id": "example-request-id"
}Common status codes#
| Status | What to check |
|---|---|
400 Bad request | Check required parameters, timestamp format, date range, sensor IDs and pagination. Use the error code to identify the invalid input. |
401 Unauthorized | missing_token: add the Bearer header. invalid_token: check the token and environment. token_expired or token_revoked: create a replacement in IRIS Cloud. |
404 Not found | Verify the resource ID and that it belongs to the token’s organization. Some requests also require an available machine configuration. |
501 Not implemented | The action-logs integration is not available yet. |
502 / 503 / 504 | A required service failed, is unavailable or timed out. For temporary failures, retry with a bounded delay and increasing backoff. Keep the request ID if the issue continues. |
Each endpoint’s reference lists its exact responses and error examples.
When Swagger cannot reach the API#
If Swagger reports Failed to fetch without an HTTP response, check the API address, your network connection and any VPN requirements. Browser requests also require the API to allow the documentation site’s origin through CORS.
Try the equivalent cURL request. If cURL works but the browser fails, share that difference with your administrator. A browser connection error does not necessarily mean the token is invalid.
Include the right details when asking for help#
Contact your usual IRIS Cloud support contact or organization administrator. Include the environment, endpoint, HTTP status, error code, request ID and the time of the request. Remove tokens and confidential response data from anything you share.