# List the tags of an order

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

- API version: v1
- Operation ID: `v1_public_sales_order_tag_index`
- Section: Sales › [Sales order tags](https://developer.yoprint.com/reference/sales-order-tags.md)
- Web page: https://developer.yoprint.com/reference/sales-order-tags/v1-sales-order-tag-index/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Returns the tags on a sales order or quote. `{hash_id}` is the order's `id` (for example `V4keXwwxMQyXw7`); the `ord_` unique key is not accepted here. This is the current way to manage order tags; there is no v2 version.

## 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/v1/api/store/your-team/sales_order/V4keXwwxMQyXw7/tag' \
  -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:
    - `color_hex` (string | null, optional): Tag color, for example `#E53935`.
    - `id` (string, optional)
    - `name` (string, optional)
- `status` (integer, required)
- `success` (boolean, required)

Example response:

```json
{
  "data": [
    {
      "color_hex": "#E53935",
      "id": "7qYPMmbLZR9oFg",
      "name": "Rush"
    }
  ],
  "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

- [Tag an order](https://developer.yoprint.com/reference/sales-order-tags/v1-sales-order-tag-attach.md): `PUT /v1/api/store/{team_slug}/sales_order/{hash_id}/tag/attach`
- [List tags](https://developer.yoprint.com/reference/tags/v1-tag-index.md): `GET /v1/api/store/{team_slug}/tag`