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

# HTTP headers

> Request and response headers for News API

This page lists the HTTP headers used in News API requests and responses.

## Request headers

| Header         | Required   | Description                                           |
| -------------- | ---------- | ----------------------------------------------------- |
| `x-api-token`  | Yes        | Your API key. Required for all requests.              |
| `Content-Type` | Yes (POST) | Must be `application/json` for POST requests.         |
| `Accept`       | No         | Set to `application/json` to request a JSON response. |

For authentication details and examples, see
[Authentication](/news-api/api-reference/authentication).

## Response headers

These headers are returned with every API response:

| Header              | Description                                                    | Example                                |
| ------------------- | -------------------------------------------------------------- | -------------------------------------- |
| `correlation-id`    | Unique identifier for tracing your request through our systems | `a702576c-2007-4b23-9ba4-cad305c84275` |
| `x-process-time`    | Server-side processing time in seconds                         | `0.7334954738616943`                   |
| `Date`              | Timestamp when the response was generated                      | `Sat, 22 Mar 2025 13:49:07 GMT`        |
| `Content-Type`      | Format of the response body                                    | `application/json`                     |
| `Transfer-Encoding` | How the response body is encoded for transfer                  | `chunked`                              |
| `Connection`        | Connection status                                              | `keep-alive`                           |
| `cf-cache-status`   | Cloudflare cache status                                        | `DYNAMIC`                              |
| `CF-RAY`            | Cloudflare ray ID for infrastructure-level tracing             | `924626834b0fbfb4-WAW`                 |
| `Content-Encoding`  | Compression applied to the response body                       | `br`                                   |
| `Server`            | Server software                                                | `cloudflare`                           |

### correlation-id

Every response includes a `correlation-id` that uniquely identifies your
request across our infrastructure. Always include it when contacting support —
it lets the team locate your exact request in the logs immediately.

```http theme={null}
correlation-id: a702576c-2007-4b23-9ba4-cad305c84275
```

For a full guide on using correlation IDs for debugging, see
[Request tracing with correlation IDs](/news-api/troubleshooting/request-tracing-correlation-ids).

### x-process-time

The `x-process-time` header shows how long the server took to process your
request, in seconds:

```http theme={null}
x-process-time: 0.7334954738616943
```

Use this to identify slow queries. Consistently high values for a specific
query are a signal to narrow the date range, simplify boolean expressions, or
reduce `page_size`.

## See also

* [Authentication](/news-api/api-reference/authentication)
* [Request tracing with correlation IDs](/news-api/troubleshooting/request-tracing-correlation-ids)
* [Rate limits](/news-api/api-reference/rate-limits)