Purchase orders
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/purchase-orders.md. Index of every page and the rules for every call: /llms.txt. Guides and concepts in one file: /llms-full.txt. OpenAPI: /openapi.json.
Read one purchase order and change its status (two operations kept for the Zapier app), its history, the CSV export and the QuickBooks sync switch. Creating, editing and receiving purchase orders is not part of the public API.
Learn more: Purchasing and stock · Work with purchase orders
5 operations
- GETList a purchase order's history
/Lists the activity recorded on a purchase order, newest first: who changed what, and when.v1/ api/ store/ {team_slug}/ purchase_order/ {hash_id}/ history - GETGet a purchase order
/Returns one purchase order with its lines, status, vendor, delivery and billing addresses, creator and tags.v1/ api/ store/ {team_slug}/ purchase_order/ {hash_id} - PUTChange a purchase order's status
/Moves a purchase order to another of the team's purchase order statuses and returns the purchase order, in the same shape as Get a purchase order.v1/ api/ store/ {team_slug}/ purchase_order/ {hash_id}/ status - PUTTurn QuickBooks sync on or off for purchase orders
/Sets whether up to 50 purchase orders sync to QuickBooks Online.v1/ api/ store/ {team_slug}/ purchase_order/ bulk_action/ mark_quickbook/ {on_or_off} - POSTExport purchase orders by issue date
/Exports the team's purchase orders whose issue date falls betweenv1/ api/ store/ {team_slug}/ purchase_order/ export start_dateandend_date.