Access Point / Host Discovery

Use the DNS widget host or an approved host discovery method before account-scoped trading requests.

What this page solves

Host selection is separate from authentication. The client needs a valid API key and the correct host before sending account-scoped trading requests.

In the current UX, the host should be visible in Key Management through the DNS widget. If a programmatic Access Point / Host Discovery method is available, use the separate Access Point YAML as the contract source.

How this fits with Key Management

Client task	Where to do it	Documentation page
Create or revoke API key	Key Management	API Key & Host Setup
Copy current host	DNS widget in Key Management	API Key & Host Setup
Resolve host programmatically	Access Point / Host Discovery API, if approved	This page and the Access Point YAML

Current review hosts

Host	Status	Notes
https://api.exness.com	main	Current configured main host for review/prototype documentation.
https://api.exness-api.com	alternative	Current configured alternative host for review/prototype documentation.

Discovery flow

1. 1
   Create and store an API key in Key Management.
2. 2
   Read the current host from the DNS widget, or sign a request to the host discovery endpoint if your integration needs programmatic discovery.
3. 3
   Use the returned or displayed host as the base URL for subsequent signed trading API requests.
4. 4
   Cache the selected host according to final Product/API guidance.

Example

Use this request-shape example only when the separate Access Point / Host Discovery YAML confirms the endpoint contract.

curl -X GET "https://api.exness.com/v1/trading/access-point?account_id=123456" \
  -H "EXN-API-KEY: exnsk_your_public_api_key" \
  -H "EXN-IDEMPOTENCY-KEY:" \
  -H "EXN-TIMESTAMP: 1773656070123" \
  -H "EXN-SIGN-VERSION: 1" \
  -H "EXN-DATA: <base64url_encoded_payload>" \
  -H "EXN-SIGN: <base64url_encoded_signature>"

{
  "access_point": "ap-qwerty123.trading.exness.com",
  "account_id": 123456
}

If host cannot be resolved

Scenario	Client action
DNS widget is unavailable	Use the currently documented static host only if Product/API guidance allows it, or wait until the host is visible.
Authentication failed	Check signed request headers and API key access.
Account not found	Check account_id and API key permissions.
Rate limited	Apply client-side throttling and retry after the limit window.
Temporary unavailability	Retry with backoff. Do not switch hosts blindly unless Product/API guidance allows it.