/manifold/markets/holders

POST /api/manifold/markets/holders

Price: 45 credits

Get the holders of a Manifold market with their shares, investment and profit

How to use it

Get who holds positions in a Manifold prediction market, ranked by shares or by profit, with each holder's YES and NO shares, amount invested, payout and profit over day, week and month.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• market string required — Manifold market id, slug or URL (examples: "BpoEJNtlQoDBpfjBmK0y", "https://manifold.markets/AndrewG/will-republicans-win-the-senate-in-738388924521"; minLength: 1)
• count integer required — Max number of holders to return (examples: 50; min: 1)
• order string — Rank holders by shares held or by profit (default: "shares"; one of: "shares", "profit")
• answer_id string nullable — Answer id of a multiple-choice market (examples: "63e3af1943d8"; minLength: 1)

Response

• @type string (default: "ManifoldHolder")
• id string required
• market_id string nullable
• answer_id string nullable
• user object nullable
  • @type string (default: "ManifoldUserRef")
  • id string required
  • alias string nullable
  • name string nullable
  • url string nullable
  • image string nullable
  • is_bot boolean nullable
• max_shares_outcome string nullable
• yes_shares number nullable
• no_shares number nullable
• yes_spent number nullable
• no_spent number nullable
• has_shares boolean nullable
• has_yes_shares boolean nullable
• has_no_shares boolean nullable
• invested number nullable
• payout number nullable
• profit number nullable
• profit_percent number nullable
• previous_profit number nullable
• loan number nullable
• margin_loan number nullable
• total_amount_invested number nullable
• total_amount_sold number nullable
• last_probability number nullable
• is_ranked boolean nullable
• period_profits array (default: [])
  • @type string (default: "ManifoldPeriodProfit")
  • period string required
  • value number nullable
  • previous_value number nullable
  • invested number nullable
  • profit number nullable
  • profit_percent number nullable
• last_bet_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 — Market 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.