GET /v1/me returns your plan, its end date and how much of each limit you use. Every response also carries the end of your paid period in the x-subscription-expires-at header.
Reads and trade calls (orders, modifications, closes, cancels) are counted separately.
The window is the calendar minute (UTC); it resets at the start of every minute.
Over the limit you get 429 RATE_LIMITED with a Retry-After header and details.retryAfter — the seconds until the minute ends. There are no other rate-limit headers.
A trade call answers 202 with a command at once. With ?wait=N (up to 60 s) it answers 200 with the final command when it finishes in time; otherwise read GET /v1/commands/{id}?wait=60 until it is final.
Limit
Value
When reached
CHECK (one-off login and read)
150 s
504 DEADLINE_EXCEEDED
Close all
120 s
504 DEADLINE_EXCEEDED
Every other trade command
60 s
504 DEADLINE_EXCEEDED
Terminal read (quotes, symbols, rates …)
?timeout, default 30 s
504 QUERY_TIMEOUT
A STANDBY account after a read with ?wait
stays logged in 60 s; a check younger than 60 s is reused
—
Keep every ?wait at 60 s or less and set your HTTP client timeout above it (for example 75 s). Never resend a trade with a new Idempotency-Key after a timeout — ask for the command first; resending with the same key is always safe.
You get the events SUBSCRIPTION_EXPIRING 3 days and 1 day before the end, then SUBSCRIPTION_EXPIRED.
After the end, requests answer 402 SUBSCRIPTION_EXPIRED and WebSockets close.
These keep working so you can always reduce risk: GET /v1/me, open positions and pending orders, closing a position, cancelling an order, close-all, and billing (invoices, one invoice, usage). Command polling (GET /v1/commands/{id}), the event feed, the WebSocket and webhooks stop — send those close calls with ?wait, or repeat them with the same Idempotency-Key, to read the result.
24 hours after the end, ACTIVE accounts go back to STANDBY. Renewing keeps the same keys and accounts.
A suspended client gets 403 CLIENT_SUSPENDED everywhere except GET /v1/me; contact support.
Your invoices and your day-by-day usage are readable through the API. All three /v1/billing routes need a key with the manage permission that is not limited to some accounts (otherwise 403 FORBIDDEN with details.permission). There is no separate plan or quota route: the plan label, the paid period and the quotas are in GET /v1/me above.
Route
Answer
GET /v1/billing/invoices
Your invoices, newest first, at most 200.
GET /v1/billing/invoices/{id}
One invoice. An unknown id or another customer's invoice answers 404 NOT_FOUND.
GET /v1/billing/usage
One row per UTC day, oldest first. ?from and ?to are days (YYYY-MM-DD), to inclusive; default: the last 30 days. A date that is not a real calendar day answers 400 VALIDATION.
GET /v1/me
Plan label (client.plan), paid period (subscription) and the quotas with their use (limits; max null = no limit) — see Your limits and usage above.
GET /v1/metrics/me
Requests, errors and trade calls of the calling key per minute (?minutes 1–10080, default 60) and its open sockets; read permission.
bash
curl https://api.propmetaapi.com/v1/billing/invoices -H "Authorization: Bearer $GW_KEY"
{
"items": [
{ "id": "9b2f…", "number": "INV-2026-000042", "clientId": "c7a1…", "plan": "pro-100", "description": "…",
"periodStart": "2026-10-04T00:00:00.000Z", "periodEnd": "2026-11-04T00:00:00.000Z", "maxActiveAccounts": 100,
"amount": 199, "currency": "USD", "status": "PAID", "paidAt": "2026-10-04T08:12:00.000Z", "paymentRef": "…", "note": null,
"createdAt": "2026-10-04T08:11:40.000Z" }
]
}
curl https://api.propmetaapi.com/v1/billing/invoices/$INVOICE_ID -H "Authorization: Bearer $GW_KEY" # one invoice (404 NOT_FOUND otherwise)
# 403 FORBIDDEN without the manage permission, or with a key limited to some accounts:
# { "code": "FORBIDDEN", "message": "billing needs the \"manage\" permission", "details": { "permission": "manage" } }
Invoice fields
Field
Meaning
number
Invoice number <prefix>-<year>-<6 digits>, e.g. INV-2026-000042; no two invoices share one.
plan
Code of the plan sold, or null.
description
What the invoice is for.
periodStart, periodEnd
The paid period this invoice sells (ISO 8601).
maxActiveAccounts
ACTIVE-account quota sold with that period.
amount, currency
Price as a number and its 3-letter currency.
status
PENDING (unpaid), PAID (then paidAt and paymentRef are set) or VOID (cancelled by the operator).
note
The operator's note, or null.
id, clientId, createdAt
Invoice id (for GET /v1/billing/invoices/{id}), your client id, creation time.
Hours your ACTIVE accounts were running that day, summed (two decimals).
accounts
Registered accounts that day.
requests
Requests counted that day, over all your keys.
tradeRequests
Trade calls counted that day.
Billing reads keep working after your plan ends — a PENDING invoice is what renews it — while commands, the event feed, the WebSocket and webhooks answer 402 SUBSCRIPTION_EXPIRED. Payment is not collected through the API: the operator marks an invoice PAID; a VOID invoice takes back the period it sold. When your plan ends · Error codes
STANDBY accounts have no connection: reads need ?wait (a short login), otherwise 409 ACCOUNT_NOT_CONNECTED. Accounts you read or trade often should be ACTIVE.
Connecting (activate) usually takes 15–60 s. Logins are paced to protect your broker connections, so activating many accounts at once is spread over a few minutes — this is expected.
Trailing stops, live risk-tracker figures and equity watches need an ACTIVE account.
MT5 only: order book (book channel), tick history, STOP_LIMIT orders, the extra timeframes (M2, M3 …) and certificates. On MT4 these answer 422 NOT_SUPPORTED_ON_PLATFORM.
Accounts can only be registered on servers of a broker the gateway knows (GET /v1/brokers; for a missing one send POST /v1/broker-requests), and the broker must be verified by one successful check before accounts on it can be activated (409 BROKER_NOT_VERIFIED).