API Key & Host Setup
Create an API key in Key Management, store the secret safely, and copy the current host from the DNS widget before making signed requests.
Where this lives in the client UI
Create credentials in Key Management and copy the current host shown by the DNS widget before sending signed requests.
API Key
Create an API key and copy the public key plus secret key.
DNS host widget
Show the current host value that this client should use for API requests. After DMS, this may be dynamic per client, region, account context, or connectivity route.
Trading account
Select the trading account or account group that the key can access.
Key Management flow
- 1Log in to Personal Area or the client portal.
- 2Open Key Management.
- 3Create a new API key.
- 4Select the key type when supported by the product UI.
- 5Fill in the key name, expiry date, trading account, and allowed IPs if these fields are enabled.
- 6Copy and securely store the API key and secret key. The secret should be shown only once.
- 7Copy the host from the DNS widget or continue to Access Point / Host Discovery if your integration resolves host values programmatically.
Values to store
| Value | Where it comes from | Client use |
|---|---|---|
EXN_API_KEY | Key Management | Identifies the API key in signed requests. |
EXN_PRIVATE_KEY | Key Management secret | Used locally by the client to create request signatures. |
EXN_ACCOUNT_ID | Selected trading account | Used in account-scoped endpoints. |
EXN_API_BASE_URL | DNS widget or host discovery | Base URL for API requests. |
Current review hosts
Use the host displayed in Key Management or returned by host discovery. Current configured static hosts are:
| Host | Status | Client action |
|---|---|---|
https://api.exness.com | Main | Use as the primary review/prototype host unless the client portal shows a different value. |
https://api.exness-api.com | Alternative | Use only when documented or displayed as the correct host for the client. |
Example
Store generated values locally as environment variables. These values are placeholders.
export EXN_API_KEY="exnsk_your_public_api_key"
export EXN_PRIVATE_KEY="your_private_secret_key"
export EXN_ACCOUNT_ID="123456"
export EXN_API_BASE_URL="https://api.exness.com"
Use Key Management for API key creation, host visibility, revocation, and rotation.
Security rules
- Store the secret key securely.
- Do not commit it to Git, paste it into chats, hardcode it in production, or include it in screenshots.
- If the secret key is lost, create a new API key.
- If the secret key is leaked, revoke the API key and create a new one.
- Use allowed IPs when the product UI supports IP restrictions.