# List invoices for export

```http
POST https://secure.yoprint.com/v1/api/store/{team_slug}/sales_order/invoices/export_list
```

- API version: v1
- Operation ID: `v1_public_sales_order_invoices_export_list`
- Section: Invoices and payments › [Invoices](https://developer.yoprint.com/reference/invoices.md)
- Web page: https://developer.yoprint.com/reference/invoices/v1-sales-order-invoices-export-list/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Returns invoice rows as JSON in `data`, one per invoice, for a date range: the invoice CSV export's columns plus a few more. `order_id` and `invoice_id` are the numbers people see, not ids. Amounts are decimal strings with 2 decimal places.

Invoices are picked by their **sales order's** issue date, not the invoice date, and only for published, non-deleted sales orders.

Send `start_date` and `end_date` as ISO 8601 date-times, for example `2026-11-01T00:00:00Z` and `2026-11-30T23:59:59Z`. They are compared as given, so a date alone means midnight UTC and an end date of `2026-11-30` leaves out most of that day.

## Permission

Needs the `view_report` permission.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.

## Request body

Content type `application/json`, required.

Fields:

- `end_date` (string (date-time), required): End of the issue date range (ISO 8601).
- `start_date` (string (date-time), required): Start of the issue date range (ISO 8601).

### Example request

```bash
curl -X POST 'https://secure.yoprint.com/v1/api/store/your-team/sales_order/invoices/export_list' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1' \
  -H 'Content-Type: application/json' \
  -d '{
    "end_date": "2026-11-30T23:59:59Z",
    "start_date": "2026-11-01T00:00:00Z"
  }'
```

## Response

`200` Successful response.

Fields:

- `data` (array of objects, required): One row per invoice; `[]` when none is in the range.
  - Each item:
    - `balance_due` (string, optional): Total minus paid. A decimal string with 2 decimal places, such as `"1250.00"`; parse it as a decimal.
    - `customer_contact_name` (string | null, optional)
    - `customer_email` (string | null, optional)
    - `customer_name` (string | null, optional)
    - `customer_tax_exempt` (string | null, optional): One of: `"TRUE"`, `"FALSE"`.
    - `delivery` (string, optional): Shipping. A decimal string with 2 decimal places, such as `"1250.00"`; parse it as a decimal.
    - `discount` (string, optional): Discount. A decimal string with 2 decimal places, such as `"1250.00"`; parse it as a decimal.
    - `invoice_id` (string, optional): The invoice number (not the id).
    - `issue_date` (string | null, optional): The invoice date, `YYYY-MM-DD`, or null.
    - `jobs` (string | null, optional): The jobs, one per line.
    - `last_payment_date` (string | null, optional): The order's last payment, `YYYY-MM-DD`, or null.
    - `order_creator` (string, optional): Created By's name, or an empty string.
    - `order_customer_in_hand_date` (string, optional): `YYYY-MM-DD`, or an empty string.
    - `order_id` (string, optional): The order number (not the id).
    - `order_issue_date` (string, optional): `YYYY-MM-DD` in the team's time zone.
    - `order_name` (string | null, optional)
    - `order_status` (string | null, optional): The order's status label.
    - `order_warehouse` (string | null, optional)
    - `paid` (string, optional): One of: `"TRUE"`, `"FALSE"`.
    - `paid_amount` (string, optional): Paid on this invoice. A decimal string with 2 decimal places, such as `"1250.00"`; parse it as a decimal.
    - `shipping_address1` (string | null, optional): The shipping address, in `shipping_label`, `shipping_address1`, `shipping_address2`, `shipping_city`, `shipping_state`, `shipping_state_code`, `shipping_country`, `shipping_country_code` and `shipping_postcode`.
    - `subtotal` (string, optional): Invoice subtotal. A decimal string with 2 decimal places, such as `"1250.00"`; parse it as a decimal.
    - `tax` (string, optional): Tax. A decimal string with 2 decimal places, such as `"1250.00"`; parse it as a decimal.
    - `tax_percentage` (string | null, optional): The tax rate in percent, such as `"8.25"`, when the invoice has one rate; otherwise null.
    - `total` (string, optional): Invoice total. A decimal string with 2 decimal places, such as `"1250.00"`; parse it as a decimal.
- `status` (integer, required)
- `success` (boolean, required)

Example response:

```json
{
  "data": [
    {
      "balance_due": "85.00",
      "customer_contact_name": "Alex Rivera",
      "customer_email": "alex@example.com",
      "customer_name": "Northwind Apparel",
      "customer_tax_exempt": "FALSE",
      "delivery": "0.00",
      "discount": "0.00",
      "invoice_id": "1001",
      "issue_date": "2026-11-03",
      "jobs": "JOB-1001 Front logo",
      "last_payment_date": "2026-11-03",
      "order_creator": "Alex Rivera",
      "order_customer_in_hand_date": "",
      "order_id": "SO1001",
      "order_issue_date": "2026-11-03",
      "order_name": "Spring team shirts",
      "order_status": "In production",
      "order_warehouse": "Main",
      "paid": "FALSE",
      "paid_amount": "50.00",
      "shipping_address1": "100 Example Street",
      "subtotal": "125.00",
      "tax": "10.00",
      "tax_percentage": "8",
      "total": "135.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`.
  - When: The role lacks `view_report`. This error has no envelope: the body is `{"message": "Insufficient Permission"}`. Fix: Ask the team owner for report permission.
- `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.
- `422` The request was refused and changed nothing. `validation_failed` lists what to fix in `error.fields`; other codes name a business rule, explained in `error.message`. A few checks answer with only `{"message": "..."}`. An operation that calls another service (a payment provider, a carrier, an accounting app) can answer `connect_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: A date is missing or not ISO 8601. Fix: Send both dates.

## Related

- [Export invoices as CSV](https://developer.yoprint.com/reference/invoices/v1-sales-order-invoices-export.md): `POST /v1/api/store/{team_slug}/sales_order/invoices/export`
- [List invoice lines for export](https://developer.yoprint.com/reference/invoices/v1-sales-order-invoices-export-all-invoice-items.md): `POST /v1/api/store/{team_slug}/sales_order/invoices/export_all_sales_order_invoice_item`