Understanding request and response headers in the NewsCatcher APIs
Header | Required | Description | Example |
---|---|---|---|
x-api-token | Yes | Your API key for authentication | x-api-token: abcd1234... |
Content-Type | Yes* | Content type of the request body (*required for POST requests) | Content-Type: application/json |
Accept | No | Preferred response format | Accept: application/json |
x-api-token
header is required for all API requests and contains your API
key:
Content-Type
header to application/json
:
Header | Description | Example |
---|---|---|
Date | When the response was generated | Date: Sat, 22 Mar 2025 13:49:07 GMT |
Content-Type | Format of the response body | Content-Type: application/json |
Transfer-Encoding | How the response is encoded for transfer | Transfer-Encoding: chunked |
Connection | Connection status between client and server | Connection: keep-alive |
x-process-time | Time taken to process the request (in seconds) | x-process-time: 0.7334954738616943 |
correlation-id | Unique identifier for tracing the request through our system | correlation-id: a702576c-2007-4b23-9ba4-cad305c84275 |
cf-cache-status | Cloudflare cache status | cf-cache-status: DYNAMIC |
Server | Server software handling the request | Server: cloudflare |
CF-RAY | Cloudflare ray ID for request tracing | CF-RAY: 924626834b0fbfb4-WAW |
Content-Encoding | Compression method used for the response body | Content-Encoding: br |
correlation-id
header contains a unique identifier for your request:
x-process-time
header shows how long it took our system to process your
request (in seconds):
x-api-token
instead
of x-api-key
for authentication.
x-process-time
values to identify
performance trends or issues.
Content-Type: application/json
header for POST requests.