Report purchase orders by issue date
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/reports/v1-report-purchase-order.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.
POST/
Returns every purchase order issued in the period, in full. Amounts (calc_subtotal, calc_tax, calc_total) are decimal strings with 4 decimal places ("125.0000").
Business rules
- A purchase order is in the period when its issue date is between
start_dateandend_date, inclusive.
Path parameters
Your team slug, shown as Team ID next to your API key in Profile.
- Example
your-team
- Example
Request body
application/json, required.
End of the period (ISO 8601), inclusive: send
23:59:59to include the whole last day. In UTC, likestart_date(an offset is dropped, not applied).Start of the period (ISO 8601), inclusive, to the second: send the start of the day. Send it in UTC (
Z): the date and time are compared with UTC as written and any offset is dropped, so2026-10-01T00:00:00-05:00means midnight UTC.
Response
200Successful response.
Fields of each item (14)
calc_subtotalstring | nullSubtotal, 4 decimal places. A decimal string, such as
"125.0000"; parse it as a decimal.calc_taxstring | nullTax. A decimal string, such as
"0.0000"; parse it as a decimal.calc_totalstring | nullTotal. A decimal string, such as
"125.0000"; parse it as a decimal.due_datestring (date-time) | nullDue date. ISO 8601 with offset, or null.
idstringThe purchase order.
issue_datestring (date-time) | nullIssue date. ISO 8601 with offset, or null.
namestring | nullpdf_urlanyPDF link with its own access token.
scoped_idstring | nullThe PO number.
status_idstring | nullThe PO status.
tax_modestring | nulltax_ratestring | nullTax rate. A decimal string, such as
"24.00000000"; parse it as a decimal.vendor_idstring | nullThe vendor.
warehouse_idstring | nullThe warehouse.
Errors
401The API key is missing or wrong (
unauthenticated).403You are not allowed to do this.
api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only{"message": "Insufficient Permission"}. Other refusals use the error envelope, withunauthorizedoruser_is_not_authorized.- When
- Your role lacks View Reports.
- Fix
- Ask the team owner to turn on View Reports for your permission group.
404Not found.
page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's.code: null, with a message that starts "No query results for": there is no record with that id.422The request was refused and changed nothing.
validation_failedlists what to fix inerror.fields; other codes name a business rule, explained inerror.message. A few checks answer with only{"message": "..."}. An operation that calls another service (a payment provider, a carrier, an accounting app) can answerconnect_timeout("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.- When
start_dateorend_dateis missing or not ISO 8601.- Fix
- Send both as ISO 8601 date-times.
Notes
- There is no paging: the whole period comes back in one response. Ask for a month or less at a time.
Related
- POSTReport sales orders by issue date
/v1/ api/ store/ {team_slug}/ report/ sales_order
