Skip to main content
ParlayX connects to Polymarket, Kalshi, ProphetX and Limitless. You integrate once and reach all four. This page covers what is true of every venue. How each one addresses a market, sizes an order and reports a fill is in its own guide.

​
Two shapes of venue

What you trade under differs by venue, and it decides how a credential reaches a pod. On Polymarket and Limitless you trade under a wallet. Each pod is created with its own wallet, so there is nothing to connect, and the wallet belongs to the pod permanently. On Kalshi and ProphetX you trade under a KYC’d account belonging to your entity. An account is connected once and then tied to the pods that may use it.

​
Connecting an account venue

1

Connect the account at the organization

An admin supplies the venue API credential. It is verified on intake and stored encrypted, with the signing key held in a hardware module.
2

Tie it to a pod

An explicit grant that lets that pod trade through that account. Untied pods cannot reach it.
3

Traders trade through the tie

Traders in the pod place orders. They never see or handle the credential.
You can connect a different account per pod, or tie one account to several pods.

​
Separation between pods

Tying one venue account to several pods gives you correct per-pod attribution in ParlayX, but the venue still sees one balance. If a strategy in one pod draws the account down, the other pods tied to it feel it. Use one account per pod when the separation needs to be real.

​
Decimal values

Prices, sizes and dollar amounts that the API returns as strings are decimals, and their number of decimal places is not fixed. The same value can come back with a different scale or different trailing zeros from one endpoint to the next, so "0.12", "0.1200" and "0.120000" can all be the same price. Compare these values as numbers, never as strings, and format them for display yourself. Where a field’s API reference description states a scale, that field keeps it.

​
Connection health

Venue credentials are monitored and surfaced in the Platform: Revoked and invalid are terminal. They are resolved by supplying a new credential, not by retrying.
A credential that has expired or been rotated at the venue cannot be detected until a call fails. If you rotate a key on the venue side, update it here at the same time.