/manifold/users

POST /api/manifold/users

Price: 1 credit

Get a Manifold user profile by username, user id or profile URL

How to use it

Get a Manifold user profile: balances in mana, deposits, follower count, traders on their markets, betting streak and verification flags. Use users/markets and users/trades for their activity.

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", "H6b5PWELWfRV6HhyHAlCGq7yJJu2", "https://manifold.markets/AndrewG"; minLength: 1)

Response

• @type string (default: "ManifoldUser")
• id string required
• alias string required
• name string nullable
• url string nullable
• image string nullable
• bio string nullable
• website_url string nullable
• twitter_handle string nullable
• discord_handle string nullable
• balance number nullable
• cash_balance number nullable
• spice_balance number nullable
• total_deposits number nullable
• total_cash_deposits number nullable
• follower_count integer nullable
• current_betting_streak integer nullable
• creator_traders object nullable
  • @type string (default: "ManifoldCreatorTraders")
  • daily integer nullable
  • weekly integer nullable
  • monthly integer nullable
  • all_time integer nullable
• fraction_resolved_correctly number nullable
• resolved_profit_adjustment number nullable
• referred_by_user_id string nullable
• referred_by_market_id string nullable
• is_bot boolean nullable
• is_admin boolean nullable
• is_trustworthy boolean nullable
• is_id_verified boolean nullable
• is_advanced_trader boolean nullable
• is_banned_from_mana boolean nullable
• is_banned_from_sweepcash boolean nullable
• is_banned_from_posting boolean nullable
• is_deleted boolean nullable
• created_at integer 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 — User 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.