Docs menu
Metaculus API endpoint
Metaculus question detail API
Returns one Metaculus question by numeric `id` (a question or post id). The response has the title, status, question type, unit, open, close and resolve times, forecaster and forecast counts, comment count, latest forecast center and bounds, categories, projects and URL.
GETapiKey2 credits/requestMetaculusmetaculus.questionResponseDoc
Metaculus/metaculus/question/{id}Endpoint facts
- Method
- GET
- API path
- /metaculus/question/{id}
- Auth
- apiKey
- Credits
- 2 credits/request
- Charged on
- Successful 2xx responses only
- Platform
- Metaculus
- Response schema
- #/definitions/metaculus.questionResponseDoc
How this endpoint behaves
Returns one Metaculus question row. id must be a numeric Metaculus question or post id.
Path parameters:
id: numeric Metaculus question or post id.
Notable response behavior:
- The response is derived from public page data, not from the authenticated Metaculus API.
- Upstream authentication, challenge, or parser drift is returned as a typed upstream error.
Live monitoring
- Monitored request
- GET /metaculus/question/42603
- Checks passed, 7 days to 14 Oct 2026
- 100%
- Median response time
- 2.96 s
Sampled response
- Request, 14 Oct 2026
- GET /metaculus/question/42603
- Items in question.projects
- 1
- Fields filled in every checked item
- 4
| Field | Filled in, of 1 checked | Values in the sample |
|---|---|---|
| id | 1 | |
| name | 1 | “Quantum Computing” |
| slug | 1 | |
| type | 1 | “question_series” |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| id (path) | string | Yes | Metaculus question or post id | 43612 | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/metaculus/question/43612" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"msg": "OK",
"data": {
"source_url": "https://www.metaculus.com/questions/43612/",
"fetched_at": "2026-06-07T14:00:00Z",
"question": {
"id": 43612,
"question_id": 43609,
"title": "Tampa sulphur price in June 2026?",
"status": "open",
"public_page_derived": true
}
}
}Request schema
No body schema
Response schema
#/definitions/metaculus.questionResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | metaculus.QuestionResponse | No | ||||
| data.fetched_at | string | No | 2026-06-07T14:00:00Z | |||
| data.question | metaculus.QuestionRow | No | QuestionRow record, 34 fields: categories, comment_count, edited_at, forecaster_count, forecasts_count, id, latest_forecast_center, latest_forecast_lower, latest_forecast_upper, open_time, projects, public_page_derived and 12 more. Described under Metaculus top comments feed API. | |||
| data.source_url | string | No | https://www.metaculus.com/questions/43612/ | |||
| msg | string | No | OK |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 500 | Internal Server Error | #/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/metaculus/question/43612" \
-H "x-api-key: $CRAWLORA_API_KEY"Shared guides
Related
More Metaculus endpoint docsMetaculus Scraper APIMetaculus category questions API documentationMetaculus comments feed API documentationMetaculus project questions API documentationMetaculus question forecast history API documentationMetaculus question forecasts API documentationMetaculus question metadata API documentation