List Purchase Order Revisions
GET/api/purchase-orders/:purchase_order/snapshots
List the immutable revision snapshots captured for a purchase order, newest first. A snapshot is recorded every time the order is sent to the supplier, so this is the complete send history of the order.
purchase-orders:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Each snapshot preserves exactly what the supplier received at that revision — the line quantities and costs, the order totals, a content hash of the sent document, who sent it and when — together with the current acknowledgement status of that revision.
Path params:
purchase_order(required): id of the purchase order.
Response: a collection under data. Each item includes revision_number, reason, submission_format, sent_to_email, sent_by_name, sent_at, acknowledgement_status (one of pending, acknowledged, changes_requested, rejected, superseded), acknowledged_at, document_hash, total_quantity and total_cost.
Authentication: Requires Bearer token.
Requires permission: purchase_orders.view
Request
Responses
- 200
- 401
- 403
- 404
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.