This page lists the HTTP headers used in News API requests and responses.Documentation Index
Fetch the complete documentation index at: https://newscatcherinc-docs.mintlify.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
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. |
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 acorrelation-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.
x-process-time
Thex-process-time header shows how long the server took to process your
request, in seconds:
page_size.