EDXM Market Data (1.0.0)

• UAT

  • https://public-api.trade.uat.edxmarkets.com/ - No Authentication Required
  • https://api.trade.uat.edxmarkets.com/ - Authentication Required

• PROD (EDX Markets)

  • https://public-api.trade.edxmarkets.com/ - No Authentication Required
  • https://api.trade.edxmarkets.com/ - Authentication Required

• PROD (EDXM Global)

  • https://public-api.trade.edxderivatives.com/ - No Authentication Required
  • https://api.trade.edxderivatives.com/ - Authentication Required

For endpoints that require authentication. API Credentials can be generated on the Clearing Member Portal via the API Apps tab with the desired permissions. With the client id and secret obtained from the clearing member portal, access tokens must be generated following OAuth2.0 standards using the client_credentials grant type. A POST request will need to be made to https://auth.{server-url}/oauth/token with the following x-www-form-urlencoded parameters

• audience: https://{server-url}/api
• grant_type: client_credentials
• client_id: {your-client-id}
• client_secret: {your-client-secret}

You can test that you can receive an access token using your credentials in UAT by making the following request:

  curl 'https://auth.uat.edxclearing.com/oauth/token' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'client_id={your-client-id}' \
  --data-urlencode 'client_secret={your-client-secret}' \
  --data-urlencode 'audience=https://uat.edxclearing.com/api' \
  --data-urlencode 'grant_type=client_credentials'

The server-url will be based on the environment:

• Prod: clearing.edxmarkets.com
• UAT: uat.edxclearing.com

This will then return a json object with one of the fields being the access_token. Provide this token in the API requests as the Authorization header with the string Bearer prepended to the token string.

Changes to this API in the following forms are considered backwards compatible and must be handled by the client application:

• Adding new fields to an existing response

• Adding new optional fields to an existing request

Client applications must not fail to deserialize responses with new properties (for example, using 'strict' JSON parsers).