Docs menu
Wccftech API endpoint
Get Wccftech section headlines API
Returns current articles from one Wccftech topic, category, or editorial archive. Pass a slug from wccftech-sections, such as topic:hardware, category:news, or archive:videos.
GETapiKey1 credit/requestWccftechpublicnews.headlinesResponseDoc
Wccftech/wccftech/headlinesEndpoint facts
- Method
- GET
- API path
- /wccftech/headlines
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Wccftech
- Execution
- Managed browser rendering where the target needs it
- Response schema
- #/definitions/publicnews.headlinesResponseDoc
How this endpoint behaves
Parameters
section (required): a current section slug from /api/v1/wccftech/sections.
Response behavior
Query parameter section is required and must exactly match a slug returned by /api/v1/wccftech/sections. Values use the dynamic category:<slug> and topic:<slug> forms or one of the four fixed archive: values documented there. Examples: topic:hardware, category:news, archive:videos.
Workflow check
Start from the checked request: GET /wccftech/headlines?section=topic%3Ahardware. Live check on 2026-10-14: 34 items returned. Fields present in every checked item: title, url, type, published_at, author, image_url.
Resolve a returned canonical story URL with Get a Wccftech article.
Live monitoring
- Monitored request
- GET /wccftech/headlines?section=topic%3Ahardware
- Checks passed, 7 days to 14 Oct 2026
- 97.7%
- Median response time
- 4.25 s
Sampled response
- Request, 14 Oct 2026
- GET /wccftech/headlines?section=topic%3Ahardware
- Items in items
- 34
- Fields filled in every checked item
- 6
| Field | Filled in, of 34 checked | Values in the sample |
|---|---|---|
| title | 34 | median 121 characters |
| url | 34 | wccftech.com |
| type | 34 | news (33), review (1) |
| published_at | 34 | 2026-10-10 to 2026-10-13 |
| author | 34 | |
| image_url | 34 | cdn.wccftech.com |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| section | string | Yes | Wccftech section slug returned by /wccftech/sections | topic:hardware | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/wccftech/headlines?section=topic%3Ahardware" \ -H "x-api-key: $CRAWLORA_API_KEY"
Illustrative JSON response shape
{
"code": 200,
"data": {
"section": "topic:hardware",
"items": [
{
"title": "Example headline",
"url": "https://wccftech.com/example-story/"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/publicnews.headlinesResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| data | newsplatform.HeadlinesResponse | No | ||||
| data.items | array | No | HeadlineItem record, 7 fields: author, image_url, published_at, summary, title, type, url. Described under Get Wccftech news API. | |||
| data.section | string | No |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
Code examples
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/wccftech/headlines?section=topic%3Ahardware" \
-H "x-api-key: $CRAWLORA_API_KEY"