Back to home

Reference

HTTP errors

All documented HTTP errors are listed here directly so users can read them without opening separate pages.

Client errors (4xx)

  • 400Bad Request

    The server cannot process the request due to malformed syntax.

  • 401Unauthorized

    Authentication is required and has failed or has not been provided.

  • 402Payment Required

    The server will not process the request until the client meets a payment or balance requirement. The MasterNode API returns 402 when prepaid workspace balance is insufficient for a billable action.

  • 403Forbidden

    The server understands the request but refuses to authorize it.

  • 404Not Found

    The requested resource could not be found on the server.

  • 405Method Not Allowed

    The request method (for example GET or POST) is not supported for this resource.

  • 408Request Timeout

    The server timed out waiting for the request.

  • 409Conflict

    The request could not be completed because of a conflict with the current state of the resource.

  • 410Gone

    The requested resource is no longer available at the server and no forwarding address is known. The MasterNode API returns 410 when chat attachment content is no longer available for preview.

  • 413Payload Too Large

    The request body is larger than the server allows.

  • 414URI Too Long

    The URI provided was too long for the server to process.

  • 415Unsupported Media Type

    The server does not support the media type or format of the requested data.

  • 422Unprocessable Content

    The server understands the content type but could not process the contained instructions.

  • 429Too Many Requests

    The client has sent too many requests in a given amount of time. The MasterNode API also uses 429 for tenant policy limits and chat rate limits.

Server errors (5xx)

  • 500Internal Server Error

    A generic error message for an unexpected server condition.

  • 501Not Implemented

    The server does not support the functionality required to fulfill the request.

  • 502Bad Gateway

    The server, while acting as a gateway, received an invalid response from an upstream server.

  • 503Service Unavailable

    The server is not ready to handle the request, often due to maintenance or overload. The MasterNode API may return 503 when shutting down, when RAG is disabled under degradation, or when an optional dependency is missing.

  • 504Gateway Timeout

    The server, while acting as a gateway, did not receive a timely response from an upstream server.

  • 505HTTP Version Not Supported

    The server does not support the HTTP protocol version used in the request.

  • 507Insufficient Storage

    The server cannot store the representation needed to complete the request.

  • 511Network Authentication Required

    The client needs to authenticate to gain network access.