Skip to main content
A purchase order records what you are buying from a supplier. These endpoints create, update, change, cancel and reactivate purchase orders, read their lines, KPIs, purchase invoices and payments, and manage their notes and attached files. This area has 23 endpoints, each available in all seven SDKs.
Deleting a purchase order or a note cannot be undone. Cancel a purchase order instead if you may need it again.

At a glance

Before you call

Register your API credentials once when your app starts, as shown in Authentication. Every SDK sample on these pages then gets its client in one line. With cURL, send the access token in an Authorization header: Authorization: Bearer $ACCESS_TOKEN.

Things to know

  • Every JSON write body is wrapped in purchase_order. The exceptions are the purchase invoice create, wrapped in purchase_invoice, and the note create, a multipart form; the cancel and reactivate calls take an empty object.
  • The note calls take the purchase order’s code, not its id. That covers listing, creating, reading and deleting notes and their files.
  • A new purchase order is active. Send "draft": true in the create body to save it as a draft instead.
  • Cancelling sets the status to inactive. Reactivating sets it back to active.
  • Listings page by cursor. Records are under data; pass pagination.next_cursor as cursor while pagination.has_more is true.
  • Notes are created as a multipart form. The text goes in the note field, and a file is optional.