# List all approvals of an order, jobs included

```http
GET https://secure.yoprint.com/v2/api/store/{team_slug}/v2/sales_order/{hash_id}/all_approvals
```

- API version: v2
- Operation ID: `v2_public_order_approval_all_approvals`
- Section: Sales › [Sales order approvals](https://developer.yoprint.com/reference/sales-order-approvals.md)
- Web page: https://developer.yoprint.com/reference/sales-order-approvals/v2-order-approval-all-approvals/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Returns every approval on a sales order or quote: the order approvals and the artwork approvals of its jobs.

An order approval asks the customer to approve the whole sales order or quote. They open it from the email or the customer portal, type their name as a signature, and approve it or ask for changes. Artwork approvals for single jobs are separate (List all approvals of an order shows both).

Shopify orders return an empty list. An old (version 1) order answers 404 here, as an unknown order does. `{hash_id}` is the order's `id` (for example `V4keXwwxMQyXw7`); the `ord_` unique key is not accepted here.

## Permission

Any member of the team.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.
- `hash_id` (string, required): The sales order's or quote's `id` (a hash id). The `ord_` unique key and the order number do not work here. Example `V4keXwwxMQyXw7`.

## Request body

This operation takes no request body.

### Example request

```bash
curl 'https://secure.yoprint.com/v2/api/store/your-team/v2/sales_order/V4keXwwxMQyXw7/all_approvals' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1'
```

## Response

`200` Successful response.

Fields:

- `data` (array of objects, required)
  - Each item:
    - `id` (string, required)
    - `status` (string | null, required): `pending` (created, not emailed), `sent-to-customer`, `viewed-by-customer`, `need-changes` or `completed` (approved). When it was completed without a `status`, the Record answer shows `null` and later reads show `""`.
    - `type` (string, required): `order` for a whole-order approval, `job` for an artwork approval. One of: `"order"`, `"job"`.
    - `approved_by` (string, optional): `contact` when a contact of the order's customer answered in the customer portal (see `approved_by_contact_id`), `user` when a team member recorded the answer (as Record the customer's answer does), `customer` otherwise, including before any answer. One of: `"contact"`, `"user"`, `"customer"`.
    - `approved_by_contact_id` (string | null, optional): The contact who answered in the customer portal, or null (always null when a team member recorded the answer).
    - `approved_by_user` (string | null, optional): The team member who recorded the answer, or null.
    - `completed` (boolean, optional): true once the customer (or you, for them) answered: approved or changes needed.
    - `completed_at` (string (date-time) | null, optional): When the customer answered. ISO 8601 with offset, or null.
    - `created_at` (string (date-time) | null, optional): Created. ISO 8601 with offset, or null.
    - `customer_last_viewed_contact_id` (string | null, optional): The contact who last opened it in the customer portal, or null when that isn't known.
    - `customer_last_viewed_date` (string (date-time) | null, optional): When the customer last opened it. ISO 8601 with offset, or null.
    - `items` (array of objects, optional): Job approvals: the mockups under review.
    - `job_id` (string | null, optional)
    - `notes_from_customer` (string | null, optional)
    - `notes_to_customer` (string | null, optional)
    - `order_id` (string, optional)
    - `order_scoped_id` (string, optional)
    - `signature` (string | null, optional): The signer's typed name.
- `status` (integer, required)
- `success` (boolean, required)

Example response:

```json
{
  "data": [
    {
      "approved_by": "customer",
      "approved_by_contact_id": null,
      "approved_by_user": null,
      "completed": false,
      "created_at": "2026-11-03T09:00:00+00:00",
      "customer_last_viewed_contact_id": null,
      "customer_last_viewed_date": null,
      "id": "xTKi8BqFVVmlL6",
      "notes_to_customer": "Please review the sizes and colors.",
      "order_id": "V4keXwwxMQyXw7",
      "order_scoped_id": "SO1001",
      "status": "sent-to-customer",
      "type": "order"
    }
  ],
  "status": 200,
  "success": true
}
```

## Errors

- `401` The API key is missing or wrong (`unauthenticated`).
- `403` You 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, with `unauthorized` or `user_is_not_authorized`.
- `404` Not 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.

## Related

- [List the order approvals of an order](https://developer.yoprint.com/reference/sales-order-approvals/v2-order-approval-index.md): `GET /v2/api/store/{team_slug}/v2/sales_order/{hash_id}/approval`
- [Filter approvals by type or status](https://developer.yoprint.com/reference/approvals/v1-approvals-filter.md): `POST /v1/api/store/{team_slug}/approvals/filter`