List approvals
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/approvals/v1-approvals-index.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.
GET/
Lists customer approvals across all of your team's sales orders and quotes, newest first.
An approval asks the customer to sign off, in the customer portal, on either a job's artwork (type job) or the whole order (type order). The customer approves or asks for changes; status follows that. Approvals are created on the order (the sales order approval operations), not here.
Draft orders, deleted orders and Shopify orders are left out. The page size is your team's list size setting (50 unless changed); use page to read further. To filter by type or status, use POST /v1/api/store/{team_slug}/approvals/filter.
Path parameters
Your team slug, shown as Team ID next to your API key in Profile.
- Example
your-team
- Example
Query parameters
pageintegerThe page to read, from 1.
- Default
1 - Minimum 1
- Default
Request body
This operation takes no request body.
Response
200Successful response.
Fields of each item (24)
approved_bystringuserwhen a team member completed it. Otherwisecustomer, even before anyone has approved it, and also when a Customer Portal contact approved it (Get an approval names the contact).- One of:
"user","customer"
- One of:
approved_by_userstring | nullThe hash id of the team member who completed it on the customer's behalf, if any.
completedbooleanTrue once the customer finished, whether they approved or asked for changes.
completed_atstring (date-time) | nullcreated_atstring (date-time)customer_idinteger | nullA plain number for the customer, not a hash id: no operation takes it. Use
order_idto reach the customer.customer_last_viewed_datestring (date-time) | nullcustomer_namestring | nullidstringjob_idstring | nullJob approvals only.
job_namestringAn empty string for order approvals.
job_scoped_idstringThe job number, such as
JOB-1001. An empty string for order approvals.notes_from_customerstring | nullnotes_to_customerstring | nullorder_external_typestring | nullorder_idstring | nullorder_namestring | nullorder_object_typestring | nullsales_orderorquote.- One of:
"sales_order","quote"
- One of:
order_quotebooleanTrue when the approval is on a quote.
order_scoped_idstringThe order or quote number.
request_bystring | nullA team member's hash id, or null. Approvals created in the web app or through the API are null here: neither records who requested them.
signaturestring | nullThe customer's signature, when they signed.
statusstringpending: not sent yet.sent-to-customer: emailed.viewed-by-customer: the customer opened it.need-changes: the customer finished and asked for changes ("Review requested").completed: approved.- One of:
"pending","sent-to-customer","viewed-by-customer","need-changes","completed"
- One of:
typestringjob: artwork approval for one job's mockups.order: approval of the whole order.- One of:
"job","order"
- One of:
paginationobjectChild fields (6)
Links to the neighbouring pages:
previousandnext, each present only when that page exists. An empty list,[], when there is only one page.
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.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.
Notes
customer_idhere is a plain number, not the hash id other operations take. To reach the customer, read the order withorder_id.completedis true for both approved and changes-requested approvals; readstatusto tell them apart.
Related
- POSTFilter approvals by type or status
/v1/ api/ store/ {team_slug}/ approvals/ filter - GETGet the approvals on an approval's order
/v1/ api/ store/ {team_slug}/ approvals/ {hash_id} - PATCHEmail an approval request to the customer
/v1/ api/ store/ {team_slug}/ approvals/ {hash_id}/ send_to_customer - POSTAsk the customer to approve an order
/v2/ api/ store/ {team_slug}/ v2/ sales_order/ {hash_id}/ approval
