---
title: "Invoices"
method: GET
path: "/v2/tasks/invoices"
tags: ["Routes", "Tasks", "Invoices"]
---

# Invoices

`GET /v2/tasks/invoices`

This request gets all Invoices associated with Tasks.

## Query parameters

- `invoices` integer
- `tasks` integer
- `start` integer
- `end` integer
- `cursor` integer
- `limit` integer

## Response `200`

Invoices

- object[]
  - `meta` object
    - `task` string
  - `invoiceID` integer
  - `file` string
  - `cost` number
  - `taskID` integer
  - `lastEdited` integer
  - `description` unknown
  - `completedDate` integer
  - `poItemID` integer
  - `invoiceFiles` object[]
    - `fileName` string
    - `link` string, uri

## Other responses

- `400` — The request was malformed — either invalid JSON syntax or a validation failure (missing required field, wrong type, etc.).
- `401` — No `Authorization` header was provided on the request.
- `403` — The supplied credentials are invalid, the customer account is inactive, or the credentials do not have permission to perform this action.
- `429` — The per-minute or per-hour rate limit for this credential and method has been exhausted. Inspect the `X-RateLimit-*` headers to determine when to retry.
- `500` — An unhandled server-side error. The body message is generic (`System unavailable...`) when the underlying cause is a database fault; otherwise it reflects the raised error.

---

[API](https://skmtc.net/limblecmms/apis/limble-api-v2.md) · [All operations](https://skmtc.net/limblecmms/apis/limble-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/limblecmms/limble-api-v2/revisions/20801e23f7f2/schema)