# Request and availability errors

Source: https://docs.graphops.xyz/platform/errors/requests

Each error below is identified by the `code` in the [error response](/platform/errors#error-response). The response's `docsUrl` links to the matching entry on this page.

## `human_principal_required`

Signed-in user required · HTTP 403 Forbidden

This request needs a signed-in user. API keys and service credentials cannot make it.

**What to do:** Sign in to the GraphOps platform or the GraphOps CLI and send the request with your session.

## `invalid_content_length`

Invalid Content-Length header · HTTP 400 Bad Request

The `Content-Length` header is not a whole number of bytes.

**What to do:** Send a valid `Content-Length` header, or let your HTTP client set it.

## `invalid_json_body`

Invalid JSON request body · HTTP 400 Bad Request

The request body is not valid UTF-8 JSON, or it is not a JSON object.

**What to do:** Send the request body as a JSON object.

## `invalid_request_body`

Unreadable request body · HTTP 400 Bad Request

GraphOps could not read the request body, usually because the connection closed during the upload.

**What to do:** Retry the request.

## `invalid_request_url`

Invalid request URL · HTTP 400 Bad Request

The request URL is malformed or too long.

**What to do:** Check the request URL and encode path and query values.

## `missing_route_parameter`

Missing path parameter · HTTP 400 Bad Request

A required identifier is missing from the request path.

**What to do:** Include every identifier the route expects, such as the organization ID.

## `organization_context_required`

Organization required · HTTP 400 Bad Request

The request does not say which organization it applies to.

**What to do:** Select an organization, or include the organization ID in the request.

## `organization_permission_insufficient`

Insufficient organization permission · HTTP 403 Forbidden

Your organization role, or the permissions of the service account that made the request, do not allow this action in this organization.

**What to do:** Ask an organization owner to change your role, or to change the service account's permissions (they belong to the account, not to its keys), or to complete the action for you.

## `request_body_too_large`

Request body too large · HTTP 413 Content Too Large

The request body exceeds the size limit for this route.

**What to do:** Reduce the size of the request body.

## `route_not_found`

Route not found · HTTP 404 Not Found

No GraphOps route matches the request host, method and path.

**What to do:** Check the request host, method and path against the documentation for the call you are making.

## `service_unavailable`

Service temporarily unavailable · HTTP 503 Service Unavailable

GraphOps could not complete the request because a platform service was briefly unavailable.

**What to do:** Retry the request after a short wait. If the error continues, check GraphOps status or contact support.

## `subgraph_response_cache_failed`

Data temporarily unavailable · HTTP 503 Service Unavailable

GraphOps could not load the requested data right now.

**What to do:** Retry the request after a short wait. If the error continues, contact support.

## `unexpected_error`

Unexpected error · HTTP 500 Internal Server Error

GraphOps hit an unexpected error while handling the request.

**What to do:** Retry the request. If the error continues, contact support and include the time of the request.

## `unsupported_content_type`

Unsupported content type · HTTP 415 Unsupported Media Type

The request body is not JSON.

**What to do:** Send the body with the `Content-Type: application/json` header.

## `validation_error`

Invalid request input · HTTP 400 Bad Request

A field in the request is missing, unsupported or has an invalid value. The message names the first problem found.

**What to do:** Correct the field named in the message and send the request again.