On this page
Polymarket’s official documentation homepage links Discord in its footer. Start from that maintained source to find the community invitation. Reviewed November 8, 2026. This guide covers finding the official route and preparing a useful question; private server channels and individual moderators have not been audited.
Find the right official resource
Open the documentation homepage, look for the Discord footer link and follow that invitation. If a copied invitation stops working, return to the source page. A search result, familiar server name or forwarded screenshot alone does not establish affiliation.
The same homepage separately links Polymarket US documentation. Match the product you use before applying instructions about accounts, funding or APIs. A community invitation does not establish trading eligibility or make instructions for one product valid for another.
Ask a precise market-resolution question
Many disagreements begin with different interpretations of the question. Before posting, write down the market URL, selected outcome, deadline, resolution source and the specific sentence you find ambiguous. Separate an event happening in the world from the narrower condition defined by a contract.
| Unclear question | More useful question |
|---|---|
| Why has this not paid? | Which official result or dispute stage remains unresolved? |
| Everyone knows Yes won | Which clause and dated source support that interpretation? |
| Why are the odds wrong? | Am I looking at a last trade, midpoint, bid, ask or model forecast? |
Community replies can identify evidence to investigate. Verify it against the published rules and source documents. Our settlement-rules guide explains how to structure that review.
Make developer questions version-specific
A useful developer report includes the API family, SDK package and version, endpoint, environment, response status and a minimal sanitized example. Current documentation includes migration guides; an old chat snippet may describe a different interface. Follow the current reference linked from the documentation index.
Never post a seed phrase, private key, API secret or signed account request. For a public-data problem, reproduce it with a public endpoint where possible. See our API overview and order-book inspection guide for research context, then confirm the present interface in official documentation.
Route account issues privately
Use the official help center to find current support instructions. A public thread is a poor place to share account documents or transaction details tied to your identity. Record the issue privately and share only what the official support route needs.
Keep a market-discussion journal
For a trade idea, record the original thesis, source date, probability range and strongest objection before seeing the result. If the outcome later differs, ask whether the evidence was weak, the price was unattractive, or the resolution definition was misunderstood. This turns a conversation into something you can learn from.
Alphascope’s forecast research and market-related news can help investigate the claim. Check the same outcome and current executable quote at the venue before making a decision.