A-MX™ API Documentation

Institutional Commodity Infrastructure API

The AgaOne A-MX™ API provides programmatic access to the full commodity trading infrastructure — from real-time precious metals pricing and trade execution to vault operations, tokenization, compliance, and physical asset verification. The APlatform Trade Bridge is the first live integration module of the A-MX™ layer, exposing the AgaOne Commodities DMCC trading engine through a single unified API. This reference documents all 12 endpoints — authentication, portfolio, tickers, prices, and full order lifecycle management.

Base URL

https://api.agaone.com/v1

All API endpoints are served over HTTPS. HTTP requests will be rejected.

The APlatform Trade Bridge uses {{baseUrl}} as configured in your integration environment. Contact AgaOne to receive the base URL for your assigned environment.

Authentication

The APlatform Trade Bridge uses a two-phase authentication flow. Phase one exchanges your API key and Client ID for a short-lived JWT trade token. Phase two uses that token as a standard Bearer credential on all subsequent endpoints.

Phase 1Auth Request

Call GET {{baseUrl}}/api/trade/auth with the two credential headers. No Authorization header is required on this call. The response returns a JWT access_token which should be stored as {{tradeToken}}.

curl -X GET "{{baseUrl}}/api/trade/auth" \
  -H "x-api-key: {{apiKey}}" \
  -H "x-client-id: {{clientId}}"

Phase 2Authorized Requests

All other endpoints require the bearer token in the Authorization header and a JSON content type.

curl -X POST "{{baseUrl}}/api/trade/portfolio" \
  -H "Authorization: Bearer {{tradeToken}}" \
  -H "Content-Type: application/json" \
  -d '{}'

Workflow

A typical Trade Bridge session follows the lifecycle below. Authenticate once, retrieve reference data, stream prices, and then manage orders through create / modify / close / cancel operations.

Quick Start

Get up and running in three steps:

curl -X GET "{{baseUrl}}/api/trade/auth" \
  -H "x-api-key: {{apiKey}}" \
  -H "x-client-id: {{clientId}}"

curl -X POST "{{baseUrl}}/api/trade/ticker-settings" \
  -H "Authorization: Bearer {{tradeToken}}" \
  -H "Content-Type: application/json" \
  -d '{}'

Platform Architecture

The AgaOne platform operates on a dual-layer architecture. A-CORE™ is the institutional ERP backbone built on Dynamics 365, serving as the system of record. A-MX™ is the orchestration and API layer that exposes platform capabilities to external integrations. A-INTELLIGENCE™ provides AI-driven compliance, risk analytics, and operational intelligence across both layers.

GET/api/trade/auth#1

Authenticate with your API credentials. Returns a JWT access_token which must be used as Bearer {{tradeToken}} in all subsequent requests. Call this first in every session.

curl -X GET "{{baseUrl}}/api/trade/auth" \
  -H "x-api-key: {{apiKey}}" \
  -H "x-client-id: {{clientId}}"

// Token capture fallback paths
payload.access_token
  || access_token
  || token
  || payload.token

No request body. The Authorization header is not required on this endpoint — only x-api-key and x-client-id.

POST/api/trade/portfolio#2

Returns the authenticated user's portfolio — balance, equity, and open positions. Send an empty JSON body.

curl -X POST "{{baseUrl}}/api/trade/portfolio" \
  -H "Authorization: Bearer {{tradeToken}}" \
  -H "Content-Type: application/json" \
  -d '{}'

// Response variables
portfolio.Balance  → portfolioBalance
portfolio.Equity   → portfolioEquity

POST/api/trade/ticker-settings#3

Returns all available trading tickers and their full configuration. The TickerID values returned here are used as the TickerId query parameter in the Prices endpoint and in Order bodies.

curl -X POST "{{baseUrl}}/api/trade/ticker-settings" \
  -H "Authorization: Bearer {{tradeToken}}" \
  -H "Content-Type: application/json" \
  -d '{}'

// Key response fields (per ticker)
TickerID          // → used as TickerId in Prices & Orders
Description       // e.g. "Gold 1 Oz", "Silver 1 Oz"
Symbol / SymbolName
MinOrderSize      // e.g. 0.01
MaxOrderSize      // e.g. 1000
PricePrecision    // decimal places for prices
QuantityPrecision // decimal places for qty

GET/api/trade/prices#4

Fetches current Bid/Ask prices for a specific ticker. The TickerId query parameter must be the numeric ID returned by Ticker Settings.

curl -X GET "{{baseUrl}}/api/trade/prices?TickerId=3" \
  -H "Authorization: Bearer {{tradeToken}}"

// Key response fields
prices[].TickerId
prices[].Bid      // → closePrice
prices[].Ask      // → openPrice (use for Buy)
prices[].Symbol

TickerId is sourced from the Ticker Settings endpoint (#3). Inspect the tickers array in that response and use the TickerID field of your desired instrument as the TickerId here.

POST/api/trade-bridge/order/create#5

Creates a market order that executes immediately at the current price. Requires Bid/Ask prices from the Prices endpoint to be fetched first. Optionally set Take Profit and Stop Loss levels.

curl -X POST "{{baseUrl}}/api/trade-bridge/order/create" \
  -H "Authorization: Bearer {{tradeToken}}" \
  -H "Content-Type: application/json" \
  -d '{
    "Side": "buy",
    "Quantity": 1,
    "TickerId": 3,
    "IsPending": false,
    "Tp": 6000,
    "Sl": 1500
  }'

POST/api/trade-bridge/order/create-pending#6

Creates a pending (limit) order that only executes when the market reaches the specified LimitPrice. The order remains open until triggered, modified, or cancelled.

curl -X POST "{{baseUrl}}/api/trade-bridge/order/create-pending" \
  -H "Authorization: Bearer {{tradeToken}}" \
  -H "Content-Type: application/json" \
  -d '{
    "Side": "buy",
    "Quantity": 2,
    "TickerId": 3,
    "IsPending": true,
    "LimitPrice": 1500,
    "Tp": 6000,
    "Sl": 500
  }'

POST/api/trade/order-history#7

Retrieves paginated order history for a given date range. Use the OrderID values from the response as input for Modify, Close, or Cancel operations.

curl -X POST "{{baseUrl}}/api/trade/order-history?pageSize=100" \
  -H "Authorization: Bearer {{tradeToken}}" \
  -H "Content-Type: application/json" \
  -d '{
    "DateFrom": "2026-03-01T00:00:00.000Z",
    "DateTo": "2026-03-25T00:00:00.000Z",
    "Culture": "en-US",
    "SearchText": ""
  }'

// Response paths (fallbacks)
history.rows[]  // or rows[] / payload.rows[]
  .OrderID      // → use for Modify / Close / Cancel
  .orderId
  .id

POST/api/trade-bridge/order/modify#8

Modifies an existing open or pending order's price, Take Profit, and/or Stop Loss. Obtain the OrderID from the Order History response.

curl -X POST "{{baseUrl}}/api/trade-bridge/order/modify" \
  -H "Authorization: Bearer {{tradeToken}}" \
  -H "Content-Type: application/json" \
  -d '{
    "OrderID": "1091",
    "Price": 3500,
    "Tp": 3600,
    "Sl": 3000
  }'

POST/api/trade-bridge/order/close#9

Closes an active open order. Supports partial closes by specifying the quantity to close in QtyToClose.

curl -X POST "{{baseUrl}}/api/trade-bridge/order/close" \
  -H "Authorization: Bearer {{tradeToken}}" \
  -H "Content-Type: application/json" \
  -d '{
    "OrderID": "1090",
    "QtyToClose": 1
  }'

POST/api/trade-bridge/order/cancel#10

Cancels a pending (limit) order that has not yet been triggered. The OrderID must refer to a pending order, not an active position.

curl -X POST "{{baseUrl}}/api/trade-bridge/order/cancel" \
  -H "Authorization: Bearer {{tradeToken}}" \
  -H "Content-Type: application/json" \
  -d '{
    "OrderID": "1091"
  }'

POST/api/trade/get-exposure#11

Returns the current exposure and risk summary across all open positions in the portfolio.

curl -X POST "{{baseUrl}}/api/trade/get-exposure" \
  -H "Authorization: Bearer {{tradeToken}}" \
  -H "Content-Type: application/json" \
  -d '{}'

POST/api/trade/get-order-info#12

Retrieves detailed information about a specific order by its ID.

curl -X POST "{{baseUrl}}/api/trade/get-order-info" \
  -H "Authorization: Bearer {{tradeToken}}" \
  -H "Content-Type: application/json" \
  -d '{
    "OrderId": "1085"
  }'

Vault Custodians

A-MX™ connects to institutional vault custodians including Brink's, Loomis, and Malca-Amit for real-time inventory synchronization, transfer orchestration, and proof-of-reserve attestation.

Banking Partners

Settlement rails connect through banking partner APIs for cross-border wire transfers, FX conversion, and real-time reconciliation across multiple currencies.

Market Data Feeds

Real-time pricing from LBMA, COMEX, Bloomberg, and Reuters feeds with sub-second latency for institutional trading operations.

Exchange Connectivity

Direct connectivity to DGCX and Borsa Istanbul for exchange-traded commodity execution and settlement.

Rate Limits

The A-MX™ API enforces rate limits to ensure fair usage across all institutional clients.

Rate limit headers are included in every response: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset

Error Codes

{
  "error": {
    "code": "INVALID_COMMODITY",
    "message": "The specified commodity 'XYZ' is not supported.",
    "status": 400
  }
}

Changelog

SDKs

Official SDKs are available for institutional integration: