> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cdp.coinbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Exchange REST API Requests

All requests and responses are `application/json` content type and follow typical HTTP response status codes for success and failure.

Note: Request URLs must be lowercase as URLs are [case-sensitive](https://www.w3.org/TR/WD-html40-970708/htmlweb.html).

## Errors

```json lines wrap theme={null}
{
  "message": "Invalid Price"
}
```

Unless otherwise stated, errors to bad requests respond with HTTP 4xx or status codes. The body also contains a `message` parameter indicating the cause. Your language's http library should be configured to provide message bodies for non-2xx requests so that you can read the message field from the body.

### Common Error Codes

| Status Code | Reason                                                        |
| :---------- | :------------------------------------------------------------ |
| 400         | Bad Request -- Invalid request format                         |
| 401         | Unauthorized -- Invalid API Key                               |
| 403         | Forbidden -- You do not have access to the requested resource |
| 404         | Not Found                                                     |
| 500         | Internal Server Error -- We had a problem with our server     |

## Success

A successful response is indicated by HTTP status code 200 and may contain an optional body. If the response has a body it is documented under each resource below.