CRISPDocs
Dashboard
Partner API

Build on CRISP

Managed Polymarket trading for your application, through your backend.

CRISP provides the trading layer; you own your product and its users' experience. Your backend provisions managed trading accounts, submits orders, retrieves portfolio and confirmed fills, and presents funding and referral rewards. Users do not need a CRISP login or leave your app for CRISP authentication.

For approved, assisted partner integrations. This documentation reflects the implemented Polymarket API reviewed on 13 September 2026. Capability flags and credential scopes determine availability. Ask CRISP for your approved endpoint, test environment and limits; do not assume a public sandbox or unrestricted access.

Quickstart

Make a signed request and provision your first managed account.

Endpoint catalogue

All 44 partner endpoints, required scopes and idempotency rules, derived from code.

Orders and portfolio

Acceptance, fills, safe retries, positions and redemption.

Launch checklist

Validate user authorization, recovery and reconciliation before live access.

How it fits

Your frontend → Your authenticated backend → CRISP Partner API → Managed execution
                       ↑                          │
                 Your user session          Account-scoped realtime
                                                  ↓
                                            Your frontend

HMAC credentials stay on your server. The credential determines the partner; there is no partner slug to put into every account or order request. Your stable externalUserId selects a user within that partner. Your backend must check the signed-in user's authority before choosing that ID. A partner key itself does not authenticate the end user.

Included capabilities

  • Headless managed accounts and optional contact/display identity.
  • Markets, books, requirements, order placement/cancel, positions and redemption.
  • Deposit instructions/quotes, balances and transfer status; approved withdrawals.
  • Confirmed fill reporting, fee programs, multi-level referrals and combined claims.
  • Scoped realtime invalidations and optional signed server webhooks.
  • Multi-tenant partner dashboard and optional website traffic ingestion.

The integration API does not provide KYC, a hosted end-user CRISP login, automatic linking to an existing CRISP account, exported signing keys, or non-Polymarket execution. CRISP's internal/admin APIs are not part of this contract.

Guides

Download the server client and machine-readable route catalogue. The catalogue is an endpoint inventory, not a complete OpenAPI schema or an automatically generated SDK.

CRISP Partner Developer Documentation

Quickstart

From server credentials to a ready managed account.

On this page

How it fitsIncluded capabilitiesGuides