/manifold/users/trades

POST /api/manifold/users/trades

Price: 20 credits

Get the trades and limit orders a Manifold user placed, newest first

How to use it

Get a Manifold user's trade history across all markets, newest first, each bet with market id, outcome, amount, shares and probability before and after. Narrow to one market, a minimum amount or only the open limit orders.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Manifold username, user id or profile URL (examples: "AndrewG", "https://manifold.markets/AndrewG"; minLength: 1)
• count integer required — Max number of trades to return (examples: 100; min: 1)
• market string nullable — Only trades on this market id, slug or URL (examples: "BpoEJNtlQoDBpfjBmK0y"; minLength: 1)
• open_limit_orders_only boolean — Only unfilled limit orders that are still open (default: false)
• min_amount number nullable — Minimum trade amount in mana (examples: 100; >: 0)

Response

• @type string (default: "ManifoldTrade")
• id string required
• market_id string nullable
• answer_id string nullable
• user_id string nullable
• outcome string nullable
• amount number nullable
• shares number nullable
• order_amount number nullable
• loan_amount number nullable
• limit_probability number nullable
• prob_before number nullable
• prob_after number nullable
• fees object nullable
  • @type string (default: "ManifoldFees")
  • creator_fee number nullable
  • platform_fee number nullable
  • liquidity_fee number nullable
• fills array (default: [])
  • @type string (default: "ManifoldTradeFill")
  • matched_bet_id string nullable
  • amount number nullable
  • shares number nullable
  • fees object nullable
    • @type string (default: "ManifoldFees")
    • creator_fee number nullable
    • platform_fee number nullable
    • liquidity_fee number nullable
  • is_sale boolean nullable
  • filled_at integer nullable
• is_filled boolean nullable
• is_cancelled boolean nullable
• is_redemption boolean nullable
• is_interest_claim boolean nullable
• is_api boolean nullable
• is_silent boolean nullable
• visibility string nullable
• bet_group_id string nullable
• reply_to_comment_id string nullable
• created_at integer nullable
• updated_at integer nullable
• expires_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 — User or 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.