Docs menu
Wccftech API endpoint
Get a Wccftech article API
Returns one Wccftech article by its canonical `url` on `wccftech.com` or `www.wccftech.com`, covering news, reviews, how-tos, roundups and best-of pages. The response has the title, description, authors, section, times, lead image and body `paragraphs` where the site serves them, plus a `paywalled` flag.
GETapiKey2 credits/requestWccftechpublicnews.articleResponseDoc
Wccftech/wccftech/articleEndpoint facts
- Method
- GET
- API path
- /wccftech/article
- Auth
- apiKey
- Credits
- 2 credits/request
- Charged on
- Successful 2xx responses only
- Platform
- Wccftech
- Response schema
- #/definitions/publicnews.articleResponseDoc
How this endpoint behaves
Parameters
url (required): canonical HTTPS Wccftech article URL.
Response behavior
Query parameter url is required. It must be an absolute HTTPS URL on wccftech.com or www.wccftech.com with a supported article path. The response contains metadata and readable body paragraphs where the publisher serves them.
Workflow check
Start from the checked request: GET /wccftech/article?url=https%3A%2F%2Fwccftech.com%2Fgigabyte-intros-three-ddr4-motherboards-for-amd-and-intel-processors-in-japan%2F. Live check on 2026-10-14: one record. Fields present in every checked record: url, title, description, published_at, updated_at, authors, image_url, paragraphs.
For a known public contributor profile, continue with Get a Wccftech author profile.
Live monitoring
- Monitored request
- GET /wccftech/article?url=https%3A%2F%2Fwccftech.com%2Fgigabyte-intros-three-ddr4-motherboards-for-amd-and-intel-processors-in-japan%2F
- Checks passed, 7 days to 14 Oct 2026
- 99.5%
- Median response time
- 2.03 s
Sampled response
- Request, 14 Oct 2026
- GET /wccftech/article?url=https%3A%2F%2Fwccftech.com%2Fgigabyte-intros-three-ddr4-motherboards-for-amd-and-intel-processors-in-japan%2F
- Fields returned with a value
- 8
| Field | In the sample | Value in the sample |
|---|---|---|
| url | Has a value | wccftech.com |
| title | Has a value | 77 characters |
| description | Has a value | 125 characters |
| published_at | Has a value | 2026-09-29 |
| updated_at | Has a value | 2026-09-29 |
| authors | Has a value | 1 entry |
| image_url | Has a value | cdn.wccftech.com |
| paragraphs | Has a value | 7 entries |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| url | string | Yes | Canonical Wccftech article URL | https://wccftech.com/gigabyte-intros-three-ddr4-motherboards-for-amd-and-intel-processors-in-japan/ | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/wccftech/article?url=https%3A%2F%2Fwccftech.com%2Fgigabyte-intros-three-ddr4-motherboards-for-amd-and-intel-processors-in-japan%2F" \ -H "x-api-key: $CRAWLORA_API_KEY"
Illustrative JSON response shape
{
"code": 200,
"data": {
"title": "Example article",
"url": "https://wccftech.com/example-story/",
"authors": [
"Reporter"
],
"paragraphs": [
"Article body paragraph."
]
}
}Request schema
No body schema
Response schema
#/definitions/publicnews.articleResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| data | newsplatform.ArticleResponse | No | ||||
| data.authors | array | No | ||||
| data.description | string | No | ||||
| data.image_url | string | No | ||||
| data.paragraphs | array | No | ||||
| data.paywalled | boolean | No | Paywalled is true when the publisher serves only a teaser of this article to anonymous readers, so Paragraphs is a partial body rather than the full text. It is omitted when the full public body was returned. | |||
| data.published_at | string | No | ||||
| data.section | string | No | ||||
| data.title | string | No | ||||
| data.updated_at | string | No | ||||
| data.url | string | No |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/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/article?url=https%3A%2F%2Fwccftech.com%2Fgigabyte-intros-three-ddr4-motherboards-for-amd-and-intel-processors-in-japan%2F" \
-H "x-api-key: $CRAWLORA_API_KEY"