Docs menu
The Next Web API endpoint
The Next Web author profile API
Returns a The Next Web author's name, image URL and the story cards on their archive page. Give `slug` or a canonical `thenextweb.com/author/<slug>` `url`; `slug` is required when `url` is omitted. Each article has a title, URL, summary, author, image, `type` and publication time.
GETapiKey2 credits/requestThe Next Webpublicnews.thenextwebAuthorResponseDoc
The Next Web/thenextweb/authorEndpoint facts
- Method
- GET
- API path
- /thenextweb/author
- Auth
- apiKey
- Credits
- 2 credits/request
- Charged on
- Successful 2xx responses only
- Platform
- The Next Web
- Response schema
- #/definitions/publicnews.thenextwebAuthorResponseDoc
How this endpoint behaves
Supply either slug or url. The author slug is required when url is
omitted. A URL must be a canonical HTTPS
thenextweb.com/author/<slug> profile URL. The response contains the public
author name and listed article cards.
Workflow check
Start from the checked request: GET /thenextweb/author?slug=darius-popa. Live check on 2026-10-14: 10 articles returned. Fields present in every checked item: title, url, author.
Return to section story discovery with Get The Next Web section headlines.
Live monitoring
- Monitored request
- GET /thenextweb/author?slug=darius-popa
- Checks passed, 7 days to 14 Oct 2026
- 99.7%
- Median response time
- 2.69 s
Sampled response
- Request, 14 Oct 2026
- GET /thenextweb/author?slug=darius-popa
- Items in articles
- 10
- Fields filled in every checked item
- 3
| Field | Filled in, of 10 checked | Values in the sample |
|---|---|---|
| title | 10 | median 62 characters |
| url | 10 | thenextweb.com |
| author | 10 |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| slug | string | No | Author slug from the public author sitemap or an article byline | darius-popa | |
| url | string | No | Canonical thenextweb.com/author/<slug> URL; alternative to slug | https://thenextweb.com/author/darius-popa | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/thenextweb/author" \ -H "x-api-key: $CRAWLORA_API_KEY"
Illustrative JSON response shape
{
"code": 200,
"data": {
"name": "Darius Popa",
"slug": "darius-popa",
"url": "https://thenextweb.com/author/darius-popa",
"articles": [
{
"title": "Example TNW headline",
"url": "https://thenextweb.com/news/example-story",
"author": "Darius Popa"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/publicnews.thenextwebAuthorResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| data | thenextweb.AuthorResponse | No | ||||
| data.articles | array | No | HeadlineItem record, 7 fields: author, image_url, published_at, summary, title, type, url. Described under The Next Web latest news API. | |||
| data.image_url | string | No | ||||
| data.name | string | No | ||||
| data.slug | 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/thenextweb/author" \
-H "x-api-key: $CRAWLORA_API_KEY"