# List the payment links of a sales order

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

- API version: v2
- Operation ID: `v2_public_sales_order_payment_link_index`
- Section: Invoices and payments › [Payment links](https://developer.yoprint.com/reference/payment-links.md)
- Web page: https://developer.yoprint.com/reference/payment-links/v2-sales-order-payment-link-index/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

A payment link (Allocations in the web app) records which invoices a payment pays: it splits payments received on the order across the order's invoices. It is not a link the customer pays through.

Returns the order's payment links with their totals (`total` is a decimal pair, usually with `dp` 4: 50.00 is `{ "value": 500000, "dp": 4 }`). A Shopify order deleted in Shopify answers 422 `shopify_order_deleted_externally`. `{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/payment_link' \
  -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): The order's payment links, not paginated.
  - Each item:
    - `id` (string, required)
    - `order_id` (string, required)
    - `total` (decimal pair, required): Total this link allocates. A decimal pair: the amount is `value` ÷ 10^`dp` (`{ "value": 125000, "dp": 4 }` is 12.50). Kept with 4 decimal places; an amount never set can come as `{ "value": 0, "dp": 0 }`. Read `dp` every time: it can differ between fields and records. See https://developer.yoprint.com/concepts/money-and-quantities.md.
    - `created_at` (string (date-time) | null, optional): Created. ISO 8601 with offset, or null.
    - `note` (string | null, optional)
    - `updated_at` (string (date-time) | null, optional): Last changed. ISO 8601 with offset, or null.
- `status` (integer, required)
- `success` (boolean, required)

Example response:

```json
{
  "data": [
    {
      "created_at": "2026-11-03T09:00:00+00:00",
      "id": "SmIWUp2A3mG3bA",
      "note": null,
      "order_id": "V4keXwwxMQyXw7",
      "total": {
        "dp": 4,
        "value": 500000
      },
      "updated_at": "2026-11-03T09:00:00+00:00"
    }
  ],
  "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

- [Create a payment link for a sales order](https://developer.yoprint.com/reference/payment-links/v2-sales-order-payment-link-create.md): `POST /v2/api/store/{team_slug}/v2/sales_order/{hash_id}/payment_link`
- [Show one payment link with allocations](https://developer.yoprint.com/reference/payment-links/v2-payment-link-show.md): `GET /v2/api/store/{team_slug}/v2/payment_link/{hash_id}`