Send Your First Request

Verify connectivity with a minimal signed GET request before sending trading operations.

Goal

Use a signed GET request to read account configuration. This verifies that the API key, signature, account access, and host are working.

Prerequisites

• API key and secret are stored securely.
• You know the account ID.
• You know the base host or resolved access point.
• You can generate EXN-DATA and EXN-SIGN.

Example

curl -X GET "https://api.exness.com/v1/configuration/accounts/123456/account" \
  -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>"

# Pseudo-code: use your validated signing helper.
headers = sign_request(
    method="GET",
    path="/v1/configuration/accounts/123456/account",
    body=None,
    idempotency_key="",
)
response = http.get("https://api.exness.com/v1/configuration/accounts/123456/account", headers=headers)

Expected response

The response should return account configuration such as account currency, leverage, margin call, stop out, and account status when supported by the YAML.

{
  "account_id": 123456,
  "currency": "USD",
  "leverage": "1:2000",
  "margin_call_level": "60",
  "stop_out_level": "0"
}

Example response needs final schema validation

Use the generated API Reference as the final source for exact response fields.

If it fails

HTTP status / code	Likely issue	Client action
401 / 1000	Invalid API key	Check key value, expiry, and account access.
401 / 1001	Invalid signature	Check payload serialization, body hash, private key, timestamp, and base64url encoding.
404 / 2000	Account not found	Check account ID and API key permissions.
429 / 1	Rate limited	Slow down requests and retry later.
503 / 2	Temporary unavailability	Retry with backoff.