Errors
The Updatify API uses standard HTTP status codes to indicate the outcome of a request.
Status codes
Section titled “Status codes”| Status | Meaning |
|---|---|
200 OK | The request succeeded. |
401 Unauthorised | The token is missing, malformed, invalid, or revoked. |
404 Not Found | The resource doesn’t exist, or it isn’t owned by your account. |
422 Unprocessable Entity | The request was understood but couldn’t be processed (e.g. invalid parameters). |
Authentication errors
Section titled “Authentication errors”Failed authentication on a protected endpoint returns 401 with a plain-text
body:
HTTP/1.1 401 Unauthorized
UnauthorisedIf a token that used to work suddenly returns 401, it has most likely been
revoked, or the account’s email address changed (tokens are bound to the email
they were issued for). See Authentication.
JSON error bodies
Section titled “JSON error bodies”Errors raised while processing a request return a JSON body. The exact shape depends on the endpoint:
{ "errors": { "details": "Unauthorised" }}The track endpoint reports failures with a success
flag instead:
{ "success": false, "errors": "Update not found"}- A
404on List project updates most often means the token belongs to a different account than the project — double-check the projectid. - Repeated
401s usually mean the token was revoked or the account email changed. Generate a new token from the API tokens page.