Start a snapshot job
Starts a job that computes an address’s holdings or an asset’s holders at any past ledger from 63 on, including before bootstrap_ledger, from a history-archive checkpoint plus at most 63 replayed ledgers. Use it when an as_of_ledger read answers 409. The job runs in the background: poll GET /snapshots/{id} (the Location header). Holders results list at most the top 10,000 holders. An organization can have at most 5 jobs queued or running. Credit class assets-snapshot: 50 per job, charged on completion and released on failure. Publishable keys are not allowed.
Authorizations
Send Authorization: Bearer <key>, the same keys as Activity and RPC. Testnet: lum_test_…; Mainnet: lum_live_…. A key works only on its own network, so pick the server that matches it (the other network answers 401). Publishable lum_pub_… keys work only on the routes marked "Publishable keys allowed", from an allowed browser origin.
Headers
Optional, 8 to 128 characters. Resending the same key with the same request returns the existing job (200, no new charge); the same key with a different request returns 409. It deduplicates on every plan, with no expiry.
8 - 128"retry-0001-2026-10-22"
Body
holdings: one address's holdings; holders: an asset's ranked holders.
holdings, holders Any past ledger from 63 up to the latest applied ledger; it may be before bootstrap_ledger.
x >= 63G or C address. Required for holdings.
Asset ID (native, CODE:ISSUER, a C… token contract or pool:<64 hex>). Required for holders.
Response
The same Idempotency-Key and request were sent before: the existing job, not charged again.
holdings, holders queued, running, completed, failed The M… address from the request, when one was sent.
A flat list of balances at as_of_ledger. Unlike the live routes it has no read_view, _links or paging.
Why the job failed.