Your event feed
const url = 'https://api.digirare.com/v1/address/example/events?limit=50';const options = {method: 'GET', headers: {'x-session-token': '<x-session-token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://api.digirare.com/v1/address/example/events?limit=50' \ --header 'x-session-token: <x-session-token>'Private owner feed of what happened to this address’s orders, newest first: listings filled/delisted/expired/invalidated (as seller), offers accepted/cancelled/expired/retired and exact authorizations used/retired (as bidder), collection offers filled/cancelled/expired/retired (as bidder), and settlements the market saw confirm (as buyer by delivery address, or as seller). Merged from several sources under one opaque keyset cursor; follow next_cursor. An event’s at is when the market observed it (a derived expiry: its expires_at), so new events arrive at the head. Dedupe on event_id and re-read a short overlap window when polling. Carries ids, txids and integer-sat prices, never a PSBT or raw transaction.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Mainnet P2TR or P2WPKH address. The SIGNING capability: every signature is verified by reconstructing a BIP-143/BIP-341 witness sighash.
Query Parameters
Section titled “Query Parameters”Opaque (created_at,id) continuation token returned as next_cursor.
Responses
Section titled “Responses”One page of the owner event feed, newest first
object
object
Stable per (kind, subject). Dedupe on it.
When the market observed it (unix seconds); a derived expiry carries its expires_at.
The subject row’s own status now.
Example
{ "result": [ { "kind": "listing_filled", "role": "seller" } ]}Stable machine-readable failure
object
On 422 mempool_rejected from a broadcast: which deterministic node policy refused the bytes. Retrying the same bytes fails the same way. fee_floor: re-quote at a higher fee_rate. chain_too_long: too many unconfirmed ancestors; wait for a confirmation, then retry. truc: a version-3 (TRUC) package rule, such as spending an unconfirmed version-3 output; wait for a confirmation, then retry.
The node’s own reject reason, on mempool_rejected (422) and on state_changed (409) when a broadcast lost to a conflicting or replacing spend.
Present and true when mempool_policy is chain_too_long or truc.
On a checkout or accept completion refused as mempool_rejected: the journaled settlement ended and every listing, bid, and asset claim it held was released (its inputs were proven unspent). The quote or accept is replaced; request a new one.
Batch listing routes only: every refused item. The first sets the status and code.
One refused item in a batch refusal’s refused_listings array. Nothing in the batch was changed.
object
On 429 rate_limited: the exact seconds until the oldest counted request leaves the window; a retry then is admitted (also sent as Retry-After). Limited writes are bucketed per route scope in exact sliding 60-second windows: by session address when a valid x-session-token is present, otherwise by IP, with a per-IP ceiling across sessions. Expensive writes: 20, ceiling 120. Signed completions: 120, ceiling 600. Session minting (/auth/*): 60 per IP. A request refused by any bucket is counted by none.
Example
{ "code": "invalid_request", "mempool_policy": "fee_floor"}