alpaca-broker-reconciliation-idempotency

Set your own client_order_id on orders and look it up via orders:by_client_order_id before retrying. For journals, send an Idempotency-Key header so the same key and body returns the original journal. Write a local intent row with the key before the network call so crashes leave a reconcilable record.

Alpaca events are at-least-once, so insert each raw event with upsert or skip-on-duplicate keyed on event_id, making duplicates no-ops. Guard business transitions by checking the record is not already terminal, lock the row while mutating, and advance the replay cursor only after successful processing.

No. Funding-wallet per-transfer status in v1beta is not pushed and must be polled via GET on the transfers endpoint. Classic wire transfers also lack a GET-by-id, so you must list outgoing transfers per account and match the ID client-side. Poll only non-terminal records.

Journals can be reversed by cashiering and transfers can be RETURNED after appearing done, and corrections issue new journal IDs carrying the real funds. Keep reconciling past the apparent terminal state for a window and confirm money movement from terminal events or polls, never from the 200 create response.

Run a nightly heal job that pages through trade activities, non-trade activities, journals, and transfers for a moving window of recent days, upserting each record keyed on its Alpaca ID. The window absorbs corrections, late settlements, and events dropped during deploys without rescanning all history.