Information
- OpenAPI version:
3.1.0
API ReferenceAPI reference
Overview
Predictefy Unified Data and Execution API 1.0.0-beta.11
Section titled “Predictefy Unified Data and Execution API 1.0.0-beta.11”Unified prediction-market DATA API: one normalized schema across every supported venue. Swap the {exchange} path segment to switch among all 16 public venues plus router (all served venues). Market schemas require honest asOf, provenance, and capabilities; event schemas declare optional asOf and provenance; order-book schemas declare optional asOf, provenance, and sourceMetadata. Other record classes expose only the fields declared by their schemas. Catalog, event, series, order-book, trade, history, and intelligence routes remain capability-qualified. The /v1/exec operations in this same contract override the default server and are served only from the isolated execution origin. Optional-field policy: null means the venue or system affirmatively knows an applicable value is absent; omission means the field is not applicable to that venue or record class.
Authentication
Section titled “Authentication”bearerAuth
Section titled “bearerAuth”API key from the Predictefy developer portal, sent as Authorization: Bearer pk_live_…. Anonymous requests answer 401 UNAUTHORIZED; a balance below the endpoint weight answers 402 INSUFFICIENT_CREDITS. Reads require their documented read scopes; every /v1/exec operation requires the trade scope.
Security scheme type: http
apiKeyAuth
Section titled “apiKeyAuth”Deprecated compatibility transport for the same Predictefy API key. Prefer Authorization: Bearer pk_live_…; when both headers are present, Bearer wins.
Security scheme type: apiKey
Header parameter name: X-API-Key