Poll events
POST
/v2.Watch/Poll
| Field | Type | Notes |
|---|---|---|
after_id | string | events after this id; 0 or absent = the oldest kept |
limit | integer | default 50, max 200 |
curl -X POST https://app.apiton.org/v2.Watch/Poll \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer 123456789:aB3dE…' \
-d '{"after_id":"122","limit":50}'
# {"events":[{"id":"123","watch_id":"41","type":"tx",…,"delivery":"none"}],"next_after_id":"123"}next_after_id as the next after_id; has_more: truemeans more are waiting. Ids only grow, so a stored cursor never skips an event. Events are kept 7
days: poll at least that often. A free key has 10 000 requests a month, which is one
Poll every4½ minutes.
delivery says what became of the event: none (the watch has no webhook) · pending (queued orbeing retried) ·
delivered (your endpoint answered 2xx) · capped (above the plan's pushes perhour: not pushed) ·
dropped (not pushed: the webhook is paused or was given up on, the watch wasdeleted, or the queue of 1000 was full). A webhook body has no
delivery.Events
Poll and in a webhook body. id, watch_id and tx.lt are 64-bit integersand arrive as JSON strings. A field with no value is absent.
type | Means | Set besides id, watch_id, address, kind, name, at |
|---|---|---|
listed | put on sale | status, owner, price, currency |
delisted | sale or auction ended with the same owner | status, owner, last price seen |
sold | sale or auction ended with a new owner | status, owner, previous_owner, last price seen |
price | the sale price changed | status, owner, price, currency |
auction_start | an auction began | status, owner, bid, bidder, auction_end |
bid | a higher bid | bid, bidder, previous_bidder, auction_end |
auction_ending | under 2 hours left; once per end time, again when a late bid moves the end | bid, bidder, auction_end |
tx | a wallet's transaction | tx, truncated |
test | from Test | what is known of the address |
listed, delisted, sold, auction_start) is reported when two readsin a row agree, so one bad read cannot fire
delisted + listed. It therefore arrives oneinterval later than a price or a bid.
{"id":"123","watch_id":"41","address":"UQCdqXGvONLwOr3zCNX5FjapflorB6ZsOdcdfLrjsDLt3AF4","kind":"wallet",
"name":"UQCdqX…3AF4","type":"tx","at":"2026-11-02T12:00:30Z",
"tx":{"hash":"9270…5c1d","lt":"113124692000006","time":"2026-11-02T12:00:11Z","success":true,"fee":0.0004,
"direction":"in","amount":10,"symbol":"TON","from":"UQAWe4m1…","to":"UQCdqX…",
"operation":"TextComment","out_messages":1}}amount and min_amount are in whole GRAM for the coin (the API's symbol for it stays TON),and in whole tokens for a jetton (
symbol is its ticker). tx is a summary: the incoming messagewhen it carries value, else the last outgoing one; the transaction's messages are in
Address/Transactions.min_amount (default 1 GRAM) is the smallest amount that raises a tx: thelargest amount among the transaction's messages, a jetton counted at its USD price. NFT and DNS
transactions always raise one.
0 = every transaction. A jetton with no known price counts asnothing; while the coin's own rate is unavailable a priced jetton passes rather than being lost.
Excess and bounce transactions raise nothing.
newest 16 and
truncated: true: the older ones have no event, read them withAddress/Transactions. Nothing else is missing compared with that RPC, but a jetton or NFT lookupabove the read's small budget leaves that transaction without its token symbol.
Request
Body Params application/jsonRequired