/metaculus/tournaments

POST /api/metaculus/tournaments

Price: 10 credits

Get a Metaculus tournament or question series by alias, id or URL

How to use it

Get one Metaculus tournament, question series or index with its prize pool, dates, scoring type, question, forecast and forecaster counts, and its description. Use tournaments/questions for its questions and leaderboards with the tournament for its standings.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tournament string required — Metaculus tournament alias, id or URL (examples: "aibq3", "3349", "https://www.metaculus.com/tournament/aibq3/"; minLength: 1)

Response

• @type string (default: "MetaculusTournament")
• id string required
• alias string nullable
• name string required
• url string nullable
• project_type string nullable
• subtitle string nullable
• text string nullable
• image string nullable
• logo_image string nullable
• prize_pool number nullable
• score_type string nullable
• visibility string nullable
• default_permission string nullable
• bot_leaderboard_status string nullable
• is_ongoing boolean nullable
• is_on_homepage boolean nullable
• is_forecasts_flow_enabled boolean nullable
• display_order integer nullable
• questions_count integer nullable
• questions_count_including_subquestions integer nullable
• forecasts_count integer nullable
• forecasters_count integer nullable
• followers_count integer nullable
• is_all_questions_closed boolean nullable
• is_all_questions_resolved boolean nullable
• last_spot_scoring_at integer nullable
• latest_actual_resolve_at integer nullable
• latest_scheduled_resolve_at integer nullable
• start_at integer nullable
• close_at integer nullable
• forecasting_end_at integer nullable
• created_at integer nullable
• edited_at integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Tournament not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.