Skip to Content
DocsError Handling

Error Handling

The Ycode API uses standard HTTP status codes to indicate the success or failure of a request.

Status codes

CodeStatusDescription
200OKThe request was successful.
400Bad RequestThe request body was incorrectly formatted. This usually means invalid JSON.
401UnauthorizedThe provided access token is invalid or does not have access to the requested resource.
404Not FoundThe requested resource was not found. Check that the collection or item ID is correct.
500Internal Server ErrorSomething went wrong on the server. Try again later.

Common causes

400 Bad Request

  • Malformed JSON in the request body
  • Missing required Content-Type: application/json header on POST/PUT/PATCH requests

401 Unauthorized

  • Missing Authorization header
  • Invalid or expired API token
  • Token has been paused or revoked
  • Token does not belong to the project being accessed

404 Not Found

  • The collection_id does not exist
  • The item_id does not exist in the specified collection
  • Typo in the API endpoint URL

500 Internal Server Error

  • Temporary server issue — retry the request after a short delay
  • If the error persists, check ycode.com  for status updates
Last updated on
Remove Item