Public API
The Pools Markets backend exposes APIs used by the extension and protocol workers. A stable third-party public API is not yet published. This page records the contract that a public release must satisfy without presenting internal endpoints as permanent.
Planned API groups
- assets and launch sources;
- current questions and market discovery;
- market detail, pools and lifecycle status;
- account positions and activity;
- settlement evidence and payout state;
- deployment and supported-chain metadata.
Compatibility requirements
A public API release must include:
- an explicit base URL and environment;
- versioned OpenAPI as the endpoint source of truth;
- authentication and authorization rules;
- pagination, sorting and filter semantics;
- rate limits and retry guidance;
- stable error codes;
- idempotency requirements for commands;
- deprecation and changelog policy.
Read purity
GET requests do not create markets, submit positions, trigger settlement or mutate checkpoints. Commands use explicit write endpoints and stable idempotency keys.
Numeric representation
Balances, prices, stakes and payouts must not rely on binary floating-point JSON numbers. APIs use integer base units or decimal strings with an explicit asset and precision.
Current status
Until the public schema is published, integrations should not depend on observed internal endpoint shapes. See Release status for publication milestones.