Skip to main content
GET
/
api
/
accounts
/
{id}
/
orders
/
history
Order history
curl --request GET \
  --url https://api.easierprop.com/api/accounts/{id}/orders/history \
  --header 'X-API-Key: <api-key>'
{
  "ok": true,
  "data": {
    "action": 0,
    "internalDeals": [
      {
        "ticket": 12345678,
        "positionTicket": 87654321,
        "type": "DealBuy",
        "entry": "DealEntryIn",
        "symbol": "EURUSD",
        "lots": 0.01,
        "openPrice": 1.08542,
        "profit": 3.2,
        "swap": 0,
        "commission": -0.07,
        "fee": 0,
        "comment": "",
        "time": "2026-04-01T12:00:00",
        "timestampUTC": 1711972800
      }
    ]
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.easierprop.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
X-API-Key
string
header
required

Client API key (prefixed with sk_). On /api/* endpoints the key is scoped to its own MT5 accounts. On /admin/* endpoints the key identifies its owning admin and grants access to all of that admin's keys — so any of your sk_ works to manage any of your other keys (cross-admin operations are rejected as 400 Key not found).

Path Parameters

​
id
string<uuid>
required

Account ID

Query Parameters

​
from
string
required

Start datetime in YYYY-MM-DDTHH:mm:ss (broker timezone). ISO-8601 inputs from Date.toISOString() (with trailing .SSSZ) are accepted — the gateway normalizes them. Malformed values return 400 INVALID_REQUEST instead of an empty result.

​
to
string
required

End datetime (YYYY-MM-DDTHH:mm:ss). Same normalization rules as from.

Response

Order history payload

​
ok
boolean
Example:

true

​
data
object

Raw mt5rest history payload. Closed positions are not pre-paired — internalDeals contains one entry per execution leg (entry/exit). Pair by positionTicket to reconstruct trades, or call /positions/{ticket}/fills for a specific position.