Developers menu

opening_read

Sent once a day per position when its alerts start: both sides' labels at that minute.

POSTyour https addressevent: opening_read
Plan ORDERSPayload unversionedSigned HMAC-SHA256Schema opening_read.schema.json

This event serves

Plan: ORDERS. Free on every finished session. Today's ledger, live, and the live POSITIONS check are the ORDERS plan. Pricing. Turn it on: The POSITIONS editor: Alert, WEBHOOK, an https address. On the Orders API and Team plans.

When it is sent

  • Once a day per position, at the first minute its alerts are on.

Payload

FieldMeaningUnit
event"opening_read"opening_read.
position_idstringThe position, p_....
daystringThe ET trading day.
tstringThe minute judged, HH:MM ET.
checkobjectThe same check GET /api/positions/check returns for the position: its phase, the expected move left, and per side the distances, the large orders near the short, the levels around it, the conditions and the label with its reason.

Delivery

AnswerAny 2xx within 3 seconds. Redirects are not followed.
RetriesOne try; no retry.
Switched offNever switched off; a failed send is logged.
VolumeOne event per label change per side per day, and one opening read.
Testevent: "test", from Send test in the editor
LogNone yet.

Verify every request before reading it: Webhooks: verify the signature.

label_changed · test

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/events/opening_read.md.