Skip to main content
POST
/
api
/
withdrawals
/
request
Initiate a withdrawal
curl --request POST \
  --url https://core.api.dev.predictstreet.sde.adifoundation.ai/api/withdrawals/request \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: <api-key>' \
  --data '
{
  "amount": "125.50",
  "destination": "<string>",
  "salt": "<string>",
  "expiry": 1729511712,
  "userSig": "<string>"
}
'
{
  "status": "PENDING",
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "code": "<string>",
  "reason": "<string>"
}

Authorizations

​
X-Api-Key
string
header
required

Partner / integrator key — format ps_live_<keyId>_<secret>. Issued by PredictStreet ops via the admin panel; never self-service. Never ship to a browser. multi_wallet partners must additionally send X-User-Wallet: 0x<40-hex> on every authenticated request to declare the acting wallet. See the API keys guide for scope taxonomy, partner kinds, rate limits, and rotation procedure.

Headers

​
X-User-Wallet
string

Required for multi_wallet partners on every authenticated request; ignored for single_wallet. Declares the acting end-user wallet for this request — drives KYC checks, balances/positions/orders attribution, rate-limit buckets, and audit. Lower-cased server-side. Missing on a multi_wallet key → 401 api_key_user_wallet_required; malformed → 401 api_key_user_wallet_invalid. The on-chain CTFExchange/Vault contracts still verify EIP-712 signer ↔ vault binding, so loosening API-layer attribution is safe by construction.

Pattern: ^0x[a-fA-F0-9]{40}$
Example:

"0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3"

Body

application/json
​
amount
string
required

USDC amount in human-readable decimal (NOT wei).

Example:

"125.50"

​
destination
string
required

Destination EOA. must match a prior cleared deposit source OR be ≥ high-value review threshold (default 5000 USDC) to route through compliance review. Use GET /api/me/withdrawals/deposit-sources to surface the allowlist before signing.

​
salt
string
required

Per-user unique uint256 salt (decimal string).

​
expiry
integer
required

EIP-712 expiry, Unix seconds.

Required range: x >= 0
Example:

1729511712

​
userSig
string
required

EIP-712 signature over { token, amount, destination, salt, deadline } against the user's vault EIP-712 domain. See Withdrawals EIP-712.

Response

OK — accepted into a routing state. Inspect status to know which.

Routing outcome. Lowercase values (rejected, mlro_review) come from the gateway when it short-circuits before reaching the exchange-service hop. Uppercase values mirror the underlying record's status (the row landed in DB).

​
status
enum<string>
required
Available options:
PENDING,
MLRO_REVIEW,
CO_SIGNED,
SUBMITTED,
CONFIRMED,
rejected,
mlro_review
​
id
string<uuid>

Created withdrawal id when status is uppercase (record exists).

​
code
string

Machine-readable rejection code (e.g. aml_block, destination_banned).

​
reason
string

Human-readable rejection reason.