> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/v1/interfaces/apis/data-product-apis/getting-started/error-codes.md).

# Error codes

Standard HTTP status codes used across all endpoints.

### Response formats

Query and perspective result endpoints support multiple output formats via a `format` query parameter, typically `json`, `yaml`, `csv`, or `parquet` (binary). Unless noted otherwise, examples in this reference use `json`.

<table><thead><tr><th width="111.922119140625">Code</th><th width="194.02642822265625">Meaning</th><th>Common cause</th></tr></thead><tbody><tr><td>400</td><td>Bad Request</td><td>Invalid SQL, wrong parameter type, or missing required field</td></tr><tr><td>401</td><td>Unauthorized</td><td>Missing or malformed Bearer token</td></tr><tr><td>403</td><td>Forbidden</td><td>You don't own this resource (e.g. updating someone else's perspective)</td></tr><tr><td>404</td><td>Not Found</td><td>Resource doesn't exist or artifact not yet generated</td></tr><tr><td>406</td><td>Not Acceptable</td><td>Unsupported result format requested</td></tr><tr><td>409</td><td>Conflict</td><td>Slug already taken when creating a perspective</td></tr><tr><td>422</td><td>Unprocessable Entity</td><td>Request body failed validation</td></tr><tr><td>429</td><td>Too Many Requests</td><td>Rate limit exceeded; back off and retry</td></tr><tr><td>502</td><td>Upstream Error</td><td>Transpiler failed to convert semantic query to SQL</td></tr><tr><td>503</td><td>Service Unavailable</td><td>Worker not ready; retry after a short wait</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/references/v1/interfaces/apis/data-product-apis/getting-started/error-codes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.