Calico API
Response Codes
Response codes are returned when interacting with our platform. These codes indicate whether your request was successful or had an error.
Response Codes: UI Examples
Successful Responses
HTML Status Code | Description | Suggested Action |
---|---|---|
201 | OK; The request has succeeded. | No action needed. Confirm the response content matches expectations |
202 | Created: The request has been fulfilled and resulted in a new source. | No action needed. Use the returned resource ID or location if applicable. |
206 | Partial Content: One or more requested crypto sources is down. | Retry the request later to notify the user about partial data availability. |
Client Error Codes
HTTP Status Code | Description | Suggested Fix |
---|---|---|
400 | Bad Request: Input does not satisfy API specification. | Validate request parameters and payload against the API documentation. |
401 | Unauthorized: Missing or invalid authentication credentials. | Ensure the access token is valid and included in the Authorization header. |
403 | Forbidden: Insufficient rights to access the resource. | Verify user permissions and requested scopes. |
404 | Not Found: The requested resource does not exist. | Check the resource ID or endpoint URL for correctness. |
429 | Too Many Requests: Rate limit exceeded. | Implement exponential backoff and retry logic. Monitor and respect rate limits. |
Server Error Codes
HTTP Status Code | Description | Suggested Fix |
---|---|---|
500 | Internal Server Error: Unexpected server issue. | Retry after a delay. If persistent, contact Calico support. |
501 | Not Implemented: Required subsystem unavailable. | Retry later or contact Calico support for system status. |
503 | Service Unavailable: Scheduled maintenance. | Retry after the maintenance window. |
End User Error Codes
HTTP Status Code | Description | Suggested Fix |
---|---|---|
601 | Customer Not Found: The specified customer does not exist. | Verify the customer ID or identifier used in the request. |
602 | Customer Not Authorized: Action not permitted for this customer. | Confirm the customer has the necessary permissions or entitlements. |
603 | Authentication Failed: Invalid credentials or session. | Prompt the user to re-authenticate. Check for expired or revoked tokens. |
701 | Account Not Found: The specified account does not exist. | Validate the account ID or ensure the account is linked to the user. |
702 | Invalid Start or End Date: Date format or logic error. | Ensure dates are in the correct format and within supported ranges. |
703 | Invalid Date Range: Start date is not earlier than end date or unsupported. | Adjust the date range to meet API requirements. |
Ready to get started?
Contact Us