> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.treet.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Codes and Messages

> Dealing with requests and responses

## Response Codes

Treet uses conventional HTTP response codes to indicate the success or failure of an API request.
In general: Codes in the **`2xx`** range indicate success. Codes in the **`4xx`** range indicate an
error that failed given the information provided (e.g., a required parameter was omitted).
Codes in the **`5xx`** range indicate an error with Treet’s servers (these are rare).

Some **`4xx`** errors that could be handled programmatically include an **error code** that
briefly explains the error reported.

## Error Codes

| HTTP Status | Error                 | Summary                                                                  |
| ----------- | --------------------- | ------------------------------------------------------------------------ |
| 400         | Bad Request           | The request was unacceptable, often due to missing a required parameter. |
| 403         | Forbidden             | The API key doesn’t have permissions to perform the request.             |
| 404         | Not Found             | The target was not found.                                                |
| 500         | Internal Server Error | Something went wrong on Treet’s end. (These are rare.)                   |

## Error Object

<ResponseField name="error" type="string">
  The error is represented in a string message.
</ResponseField>