Developers menu

ORDERS: Orders API and POSITIONS API

The order ledger and the POSITIONS check from code, with an orders key on the Orders API or Team plan. The same rows the ORDERS panel draws, and the same reading the POSITIONS panel shows.

This product serves

Plan: ORDERS. Free on every finished session. Today's ledger, live, and the live POSITIONS check are the ORDERS plan. Pricing.

Rows come sorted by what the order did to the book, which is not the size of the cheque: over 661 sessions with the full 0DTE tape the rank correlation between premium and effect on the book is -0.03.

Between a quarter and a half of the orders carry no side: the package rule could not orient them, and the row leaves lg signs at 0 rather than guess. stats.no_side and stats.no_gamma count them for the session.

SPX only: an order is placed against the measured book, signed from the trade tape, and SPX is the only root that has one.

Endpoints

More

  • Orders MCP server: An assistant reads the ledger directly from https://firmtape.com/orders/mcp, with the orders key in the same header and on the same daily budget.

Webhook events

TypeSent when
label_changedSent when a side of a position changes its label (TRADE, CAUTION, SKIP).
opening_readSent once a day per position when its alerts start: both sides' labels at that minute.
testSent by Send test in the POSITIONS editor, signed the same way.

Every event of ORDERS · Signing, retries, test

Limits

WhatLimitNotes
Orders API and POSITIONS API20,000 calls a day on Orders API, 100,000 on Orders Team, per accountThe count resets at midnight ET. The Orders MCP server counts against the same budget.

Measurements of dealer positioning, never a forecast or a trade call. This page is built from FirmTape's public contract, the same files the OpenAPI document is built from; the tests hold them against the route code. Markdown: /docs/developers/orders.md.