Skip to main content
PredictStreet’s integrator API uses a two-layer authentication model:
  1. Session auth — API key. Your server holds an issued key and sends it as X-Api-Key: ps_live_<keyId>_<secret> on every request. See API keys.
  2. Per-operation auth — EIP-712. Every operation that moves funds (placing orders, vault split / merge) additionally requires an EIP-712 signature over the operation’s typed data. An API key alone is never sufficient to move money. Each order, split and merge is signed with the private key of the acting wallet: your associatedWallet for single_wallet partners, or the wallet named in X-User-Wallet for multi_wallet partners. In the signed Order struct that wallet is the signer, its vault is the maker, and signatureType is 1.
This split gives you stable long-lived credentials for the HTTP layer while keeping cryptographic finality for writes — a compromised API key cannot drain a vault, because the private key that signs the EIP-712 authorisation never leaves your infrastructure.
Retail user logins live on a separate surface. End users sign in on the web app (app.dev.predictstreet.sde.adifoundation.ai on testnet, adipredictstreet.com on mainnet), which issues its own short-lived session token. Partner integrations do not use or implement that login; they authenticate with API keys only.
One key, many wallets. Trading firms with N sub-accounts, copy-trading platforms, and custodial brokers can request a multi_wallet partner kind — one API key fans out across many end-user wallets, with the actor declared on each request via X-User-Wallet. See Partner kinds for the contract.

Flow at a glance

Base URL

Retail user traffic (the web app — app.dev.predictstreet.sde.adifoundation.ai on testnet, adipredictstreet.com on mainnet) is a separate surface and isn’t documented here.

Where to next

API keys

Format, scope taxonomy, endpoint coverage, rotation procedure.

Rate limits

Per-partner, per-wallet, per-IP buckets.

EIP-712 signing

How the per-operation order signature works.

Quickstart

First order end-to-end with an API key.