digitalocean
DigitalOcean API Error Codes
Error identifiers returned in the `id` field of DigitalOcean API v2 error responses. Every 4xx/5xx response body is a JSON object with an `id` naming the error class and a human-readable `message`.
7 codes
· All codes 7 codes
- bad_request Bad Request The request could not be understood by the server, typically due to malformed JSON in the request body or a missing required field. Check the request body against the endpoint's documented schema.
- forbidden Forbidden The authenticated token does not have access for the attempted action, such as a read-only token used on a write endpoint, or a token scope that excludes the requested resource. Issue a token with the required scope.
- not_found Not Found The requested resource, such as a Droplet, volume, or domain, could not be found. Either it does not exist or the token does not have access to it. Verify the resource ID and the account it belongs to.
- server_error Server Error An unexpected error occurred on DigitalOcean's servers while processing the request. This is not caused by the request itself; retry with backoff, and check the DigitalOcean status page if the error persists.
- too_many_requests Too Many Requests The client has exceeded the API rate limit. Current limits are returned in the RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset response headers. Back off and retry after the reset time, ideally with exponential backoff.
- unauthorized Unauthorized The API request could not be authenticated. The bearer token in the Authorization header is missing, malformed, or invalid. Generate a new personal access token or OAuth token and retry.
- unprocessable_entity Unprocessable Entity The request was well-formed but failed validation, such as a name that is already taken, a value outside the allowed range, or a reference to a resource in an incompatible region. The message field describes the specific validation failure.