# List invoice lines for export

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

- API version: v1
- Operation ID: `v1_public_sales_order_invoices_export_all_invoice_items`
- 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-all-invoice-items/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Returns the invoice lines that come from order lines, one row per line, as JSON in `data`, for a date range. Tax, shipping, discount and fee lines of an invoice are not listed, and the rows' `tax`, `discount` and `tax_percent` are always null. `order_id` and `invoice_id` here are hash ids; the numbers are `order_scoped_id` and `invoice_scoped_id`. Amounts are thousandths as strings, an older encoding: `"12500"` is 12.50. See [Money and quantities](/concepts/money-and-quantities/).

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

Here the range covers whole days: `start_date` from midnight, `end_date` to the end of its day (UTC). Send ISO 8601 dates, such as `2026-11-01` and `2026-11-30`.

## 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_all_sales_order_invoice_item' \
  -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-30",
    "start_date": "2026-11-01"
  }'
```

## Response

`200` Successful response.

Fields:

- `data` (array of objects, required): One row per invoice line that comes from an order line; `[]` when none is in the range.
  - Each item:
    - `discount` (null, optional): Always null.
    - `has_empty_product_cost` (boolean, optional)
    - `invoice_id` (string, optional): The invoice's `id` (a hash id).
    - `invoice_scoped_id` (string, optional): The invoice number.
    - `job_name` (string, optional): The line's job name, or an empty string.
    - `order_creator` (string, optional): Created By's name, or an empty string.
    - `order_creator_id` (string, optional): Created By's user id, or an empty string.
    - `order_date` (string, optional): The order's issue date, `YYYY-MM-DD` in the team's time zone.
    - `order_id` (string, optional): The order's `id` (a hash id).
    - `order_name` (string | null, optional)
    - `order_scoped_id` (string, optional): The order number.
    - `order_status` (string | null, optional): The order's status label.
    - `order_warehouse` (string, optional): The order's warehouse label.
    - `product_cost` (string, optional): Cost of one unit. Thousandths as a string, an older encoding: `"12500"` is 12.50. See [Money and quantities](/concepts/money-and-quantities/).
    - `product_name` (string | null, optional)
    - `product_total` (string, optional): Product price of one unit. Thousandths as a string, an older encoding: `"12500"` is 12.50. See [Money and quantities](/concepts/money-and-quantities/).
    - `product_type` (string, optional): The line's kind.
    - `quantity` (integer | string, optional): The quantity: a whole number, or a decimal string.
    - `service_total` (string, optional): Decoration price of one unit. Thousandths as a string, an older encoding: `"12500"` is 12.50. See [Money and quantities](/concepts/money-and-quantities/).
    - `services` (string, optional): The job's decoration services, comma-separated.
    - `status` (object | null, optional): The order's status record, as stored (not the status answer shape).
    - `subtotal` (string, optional): The invoice line's subtotal. Thousandths as a string, an older encoding: `"12500"` is 12.50. See [Money and quantities](/concepts/money-and-quantities/).
    - `tax` (null, optional): Always null: this export has no tax per line.
    - `tax_percent` (null, optional): Always null.
    - `total` (string, optional): The same as `subtotal`. Thousandths as a string, an older encoding: `"12500"` is 12.50. See [Money and quantities](/concepts/money-and-quantities/).
- `status` (integer, required)
- `success` (boolean, required)

Example response:

```json
{
  "data": [
    {
      "discount": null,
      "has_empty_product_cost": false,
      "invoice_id": "QRbvVd2ZKcvSTB",
      "invoice_scoped_id": "1001",
      "job_name": "Front logo",
      "order_creator": "Alex Rivera",
      "order_creator_id": "PydH0WtBhSeiNU",
      "order_date": "2026-11-03",
      "order_id": "V4keXwwxMQyXw7",
      "order_name": "Spring team shirts",
      "order_scoped_id": "SO1001",
      "order_status": "In production",
      "order_warehouse": "Main",
      "product_cost": "6000",
      "product_name": "Team shirt",
      "product_total": "12500",
      "product_type": "user_simple",
      "quantity": 10,
      "service_total": "0",
      "services": "Screen print",
      "subtotal": "125000",
      "tax": null,
      "tax_percent": null,
      "total": "125000"
    }
  ],
  "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

- [List invoices for export](https://developer.yoprint.com/reference/invoices/v1-sales-order-invoices-export-list.md): `POST /v1/api/store/{team_slug}/sales_order/invoices/export_list`
- [Export invoice line items in a date range to CSV](https://developer.yoprint.com/reference/data-exports/v1-data-export-export-invoice-item.md): `POST /v1/api/store/{team_slug}/data_export/export_invoice_item`