ProphetX API: what it exposes, how it authenticates, where it stops

What the API exposes

The Trading API (versioned v2 and v4 paths under /partner) submits single or multiple orders with strategies such as fillOrKill, cancels by order, event or market, reads order history and matched details, price ladders, balances and wallet transactions, and lists tournaments, sport events, markets and strikes.

Real-time data arrives over a WebSocket that speaks the Pusher wire protocol. Call GET /websocket/connection-config, connect, then POST /mm/websocket with your socket ID to receive signed per-event and per-prop channels. ProphetX is moving this feed to Talaria, its in-house server, with a September 16, 2026 production cutover; the wire protocol stays the same.

The Parlay API delivers RFQs over the socket for market makers to quote and confirm. The Market Data API is offered to display partners on request.

Authentication and rate limits

Create tokens under the API integration menu in the ProphetX UI; each token is an access key plus secret key. POST /auth/login exchanges them for a session and POST /auth/refresh renews the access token. Sandbox base URL is https://api.sandbox.prophetx.dev/partner; production is https://cash.api.prophetx.co/partner.

Rate limits exist but numbers are not published. The market data guide says to keep an eye on rate limits and to contact your ProphetX contact for a higher one.

Pricing and access

Trading API access starts with a request form on the ProphetX Zendesk, or by emailing hello@prophetexchange.com; market data access goes through a named market data contact. The sandbox account at ss-sandbox.prophetexchange.com/register needs a real phone for 2FA and is funded with demo money on request.

No API fee or trading fee figures appear in the developer docs. A GitHub integration guide (betprophet1/mm-api-integration-guide) and a bot skeleton walk through login, market fetch, WebSocket subscription and order submission.

Where it falls short

Access is gated by human review, and neither rate limits nor fees are published.

Two endpoint generations coexist (wager-named v2 routes and order-named v4 routes) and the WebSocket backend is mid-migration, so integrations need to track the changelog.

Coverage is sports only, and the sandbox is the only way to test without production funds.

Who should use it

Market makers and parlay pricers who want regulated US sports flow and are prepared for an onboarding conversation.

Hobbyists who want a self-serve key will find Novig or SX Bet lighter to start with.