alpaca-broker-journals

Create a JNLC journal with POST /v1/journals, passing from_account, to_account, and amount as a decimal string. Cash journals work in both directions between firm and user accounts but not customer-to-customer.

Send an Idempotency-Key header, ideally a UUID derived from your own transaction ID, on every journal create. The same key with an identical body returns the original journal, while the same key with a different body returns a 422 error.

JNLC moves cash between firm and user accounts in either direction and requires an amount field. JNLS moves whole or fractional shares from firm to user accounts only and requires symbol and qty fields.

The executed status means balances updated, but Alpaca cashiering can still reverse the journal. A correction cancels the original and creates a new journal with a different ID, so reconciliation must be event-driven and keyed by journal ID.

DELETE /v1/journals/{id} only works while the journal is pending and returns 422 after execution. To reverse an executed journal, create a mirror journal in the opposite direction instead of deleting.

Journals only move value between accounts inside your own Alpaca omnibus and never touch external banks. For deposits or withdrawals to external bank accounts, use the funding-transfers endpoints instead.