Build trading and partner workflows on Exness APIs

Explore generated API references for partner operations, campaign data, rebates, balances, conversions, venues, market data, and more.

Start Building View API Reference

Quick Start

Pick the API surface you need, authenticate with your Exness credentials, and make your first request from the generated reference.

Choose an API

Start with the Partnership API for affiliate, campaign, report, wallet, and rebate workflows, or the Trading API for venue, balance, conversion, rate, and market data workflows.

Prepare credentials

Create or request the credentials for the environment you are integrating with. Keep tokens server-side and avoid exposing them in browser clients or public repositories.

Send a request

Use the base URL and authentication scheme shown in the selected API reference.

curl --request GET "$EXNESS_BASE_URL/trade/v1/balances" \
  --header "Authorization: Bearer $EXNESS_API_TOKEN" \
  --header "Accept: application/json"

Handle responses

Check status codes, pagination fields, and asynchronous job states before moving money, changing campaigns, or reconciling reports.

Example response shape

{
  "data": [],
  "pagination": {
    "page": 1,
    "size": 25
  }
}

API Reference

Browse endpoint definitions, parameters, request bodies, response schemas, and interactive playgrounds for each API product.

Partnership API

Affiliate, partner, campaign, report, wallet, traffic source, and rebate endpoints for partner operations.

Trading API

Layer1 trading endpoints for conversions, venues, balances, rates, withdrawals, deposits, and market data.

Build With Confidence

The docs are organized around the operational paths developers need most: customer acquisition, trading infrastructure, movement of funds, and reporting.

Partner Growth

Track campaigns, partner links, traffic sources, client reports, and reward programs.

Trading Operations

Create conversions, monitor balances, request venue addresses, and fetch indicative rates.

Clear Schemas

Use generated OpenAPI schemas and playgrounds to validate requests before production rollout.

Ready to Integrate?

Jump into the generated reference, inspect endpoint contracts, and test requests in the interactive playground.

Explore Docs

Documentation Index