Skip to main content
No. polymarket-data is community-maintained and not endorsed by the Polymarket team. It targets public endpoints published by Polymarket. Confirm contractual or compliance requirements with Polymarket before deploying to production.
Not for the endpoints currently implemented. If Polymarket introduces authentication, the community will update the SDK accordingly.
  • Node.js 18+ (native fetch)
  • Serverless runtimes that support ESM modules
  • Browser environments, provided CORS allows the target endpoints
Supply a custom fetch implementation if your runtime does not expose one.
Every request and response flows through Zod schemas. Unexpected payloads throw descriptive errors, helping you spot upstream changes immediately.
Zod validation will fail with a message like:
Invalid response for gamma.markets.listMarkets: …
Capture the new payload, open an issue, and submit a PR updating the schema. Include unit/integration tests to lock the change in place.
  1. Fork the repository.
  2. Model the endpoint in Zod.
  3. Implement the method and export types.
  4. Add unit/integration tests.
  5. Run lint, build, and test scripts.
  6. Submit a detailed pull request.
Polymarket’s public APIs may enforce rate limits. Cache responses where possible and avoid excessive polling. Consult Polymarket’s official docs for the latest policies.