> ## Documentation Index > Fetch the complete documentation index at: https://docs.envoi.no/llms.txt > Use this file to discover all available pages before exploring further. # List invoices > The account's invoices and credit notes, most recently created first, a page at a time. Drafts are included. For a sync, pass `updatedSince` with the time of your last sync: you get every invoice that changed at or after it. Offset paging over a stable order; an invoice created while you page can shift later pages by one. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/invoices openapi: 3.0.4 info: title: Envoi API description: >- The Envoi API lets your own systems work with an Envoi account: create and send invoices, record payments, keep the customer register in step, and read the books. An online store such as Nordvik Handel AS can, for example, create an invoice in Envoi for every B2B order from its web shop and mark it paid when the money arrives. **Base URL.** `https://api.envoi.no`. Every path starts with `/v1`. **Authentication.** An Owner or Admin creates an API client in Envoi under *Settings → API clients* (in the app: *Innstillinger → API-klienter*) and gets a Client ID and a client secret (shown once). Exchange them for an access token at `POST /v1/oauth/token` (OAuth 2.0 client credentials) and send it as `Authorization: Bearer {access_token}`. A token lives 15 minutes; ask for a new one when it expires. Every request is checked against Envoi's database, not only the token: deleting the client, rotating its secret or removing a scope takes effect on the next request. **Accounts and environments.** A token acts on one account, named by its Account ID in the token request's `audience`: `P11112001` is the production account, `T11112001` its test environment. Nothing done in the test environment reaches a real customer: emails are captured, not delivered. An id from another account, or from the other environment, is `404 not-found`, never `403`. **Scopes.** Each endpoint needs one scope, such as `invoices:read`. Levels nest: `admin` includes `write`, `write` includes `read`. A request without the scope is `403 insufficient_scope`. **Errors.** Every error is JSON: `{ "code": "...", "message": "..." }`, sometimes with `details`, and with `errors` (one entry per field) on `400 validation-failed`. Branch on `code`; the message is for developers and may change. The token endpoint uses the OAuth shape `{ "error": "..." }` instead. **Idempotency.** Every POST needs an `Idempotency-Key` header. A retry with the same key and the same request gets the first answer again instead of creating a second invoice or payment. **Paging.** Lists take `page` (from 1) and `pageSize` (1 to 100) and answer `{ "items": [...], "page": 1, "pageSize": 20, "totalCount": 57, "hasMore": true }`. **Values.** JSON in camelCase. Dates are `yyyy-MM-dd`; timestamps ISO 8601 in UTC. Money is in kroner as a decimal number; `currency` is always `NOK` in v1. VAT codes are the SAF-T standard codes (for sales: `3` = 25 %, `31` = 15 %, `33` = 12 %, `5` = exempt, `6` = outside the VAT Act, `7` = no VAT treatment, `52` = export). **Rate limits.** Each API client may send 600 requests a minute; the token endpoint allows 60 requests a minute per IP address and 30 per Client ID. Above that the answer is `429` with a `Retry-After` header. version: v1 servers: - url: https://api.envoi.no description: >- Production and test environment (the token's audience picks the environment) security: [] tags: - name: Authentication description: >- Get an access token with the OAuth 2.0 client credentials grant, and see which API client and account a token belongs to. - name: Invoices description: >- Create draft invoices, send them, record payments, and read invoices. The same rules as in the Envoi app. - name: Clients description: The account's customer register. - name: Accounting description: >- Read-only views of the built-in books: the chart of accounts and journal entries. Only when Envoi's built-in accounting is turned on for the account. paths: /v1/invoices: get: tags: - Invoices summary: List invoices description: >- The account's invoices and credit notes, most recently created first, a page at a time. Drafts are included. For a sync, pass `updatedSince` with the time of your last sync: you get every invoice that changed at or after it. Offset paging over a stable order; an invoice created while you page can shift later pages by one. operationId: listInvoices parameters: - name: page in: query description: The page, from 1. schema: minimum: 1 type: integer format: int32 default: 1 example: 1 - name: pageSize in: query description: Invoices per page, 1 to 100. schema: maximum: 100 minimum: 1 type: integer format: int32 default: 20 example: 20 - name: status in: query description: >- Only invoices with this status: `draft`, `sent`, `viewed`, `paid`, `overdue`, `reminded`, `collection_warning`, `credited` or `bounced`. schema: type: string example: sent - name: updatedSince in: query description: Only invoices changed at or after this time (ISO 8601). schema: type: string format: date-time example: '2026-09-01T00:00:00Z' responses: '200': description: A page of invoice summaries. content: application/json: schema: $ref: '#/components/schemas/InvoiceSummaryPage' example: items: - id: 8b6f2a4e-1c3d-4e5f-9a7b-2c4d6e8f0a12 number: '10023' type: invoice status: sent clientName: Fjordkaffe AS issueDate: '2026-09-29' dueDate: '2026-10-13' total: 1250 paidAmount: 0 updatedAt: '2026-09-29T10:15:00Z' creditedAmount: 0 outstandingAmount: 1250 page: 1 pageSize: 20 totalCount: 1 hasMore: false '400': description: >- - `validation-failed`: `page` below 1 (`greater-than-or-equal`), `pageSize` outside 1 to 100 (`out-of-range`), or an unknown `status` (`unknown-status`). content: application/json: schema: $ref: '#/components/schemas/Error' examples: validation-failed: summary: validation-failed value: code: validation-failed message: The request is not valid. errors: - field: status code: unknown-status '401': description: >- - `unauthorized`: no token, an invalid or expired one, or a token the per-request check refuses (the client or its grant was deleted, the secret was rotated, or the account is being closed). Header `WWW-Authenticate: Bearer error="invalid_token"`. content: application/json: schema: $ref: '#/components/schemas/Error' examples: unauthorized: summary: unauthorized value: code: unauthorized message: A valid API client access token is required. '403': description: >- - `insufficient_scope`: the grant does not hold `invoices:read` (or a higher level of it). content: application/json: schema: $ref: '#/components/schemas/Error' examples: insufficient_scope: summary: insufficient_scope value: code: insufficient_scope message: This API client needs invoices:read. '429': description: >- - `rate_limited`: this API client sent too many requests. Wait the number of seconds in `Retry-After`. headers: Retry-After: description: Seconds to wait before the next request. schema: type: integer content: application/json: schema: $ref: '#/components/schemas/Error' examples: rate_limited: summary: rate_limited value: code: rate_limited message: Too many requests; try again later. '500': description: >- - `server-error`: something unexpected went wrong. The message never contains details. On a POST the `Idempotency-Key` is released, so retrying with the same key is safe. content: application/json: schema: $ref: '#/components/schemas/Error' examples: server-error: summary: server-error value: code: server-error message: >- The request could not be completed. It is safe to retry with the same Idempotency-Key. security: - oauth2: - invoices:read - bearerAuth: [] components: schemas: InvoiceSummaryPage: required: - hasMore - items - page - pageSize - totalCount type: object properties: items: type: array items: $ref: '#/components/schemas/InvoiceSummary' description: The items on this page. page: type: integer description: This page's number, from 1. format: int32 pageSize: type: integer description: The page size asked for. format: int32 totalCount: type: integer description: How many items there are on all pages together. format: int32 hasMore: type: boolean description: True when there is a next page. description: One page of a list. Error: required: - code - message type: object properties: code: type: string description: >- A stable, machine-readable code, for example `not-found` or `insufficient_scope`. Branch on this, never on the message. message: type: string description: >- A short English sentence for a developer. Never contains customer data and may change. details: type: object additionalProperties: {} description: >- Extra facts for some codes, for example `existingId` on `client-exists`, `outstanding` on `payment-exceeds-outstanding`, `maxMonths` on `period-too-long`. Absent otherwise. nullable: true errors: type: array items: $ref: '#/components/schemas/FieldError' description: >- Present only on `validation-failed`: one entry per field that failed. nullable: true description: The error body of every `/v1` endpoint except the token endpoint. InvoiceSummary: required: - clientName - creditedAmount - dueDate - id - issueDate - outstandingAmount - paidAmount - status - total - type - updatedAt type: object properties: id: type: string description: The invoice's id. format: uuid number: type: string description: The invoice number, or null on a draft. nullable: true type: type: string description: '`invoice` or `credit_note`.' status: type: string description: The invoice's status, as on `Invoice`. clientName: type: string description: The client's name. issueDate: type: string description: The invoice date. format: date dueDate: type: string description: The due date. format: date total: type: number description: Total with VAT. paidAmount: type: number description: How much has been paid. updatedAt: type: string description: When it last changed (UTC). format: date-time creditedAmount: type: number description: The issued credit notes against the invoice. outstandingAmount: type: number description: >- How much is still owed: total minus credited minus paid, 0 once paid or fully credited. description: An invoice in a list. FieldError: required: - code - field type: object properties: field: type: string description: >- The field's path in the request, for example `dueDate` or `lines[0].quantity`. code: type: string description: A stable kebab-case code, for example `required` or `greater-than`. description: A field that failed validation. securitySchemes: oauth2: type: oauth2 description: >- OAuth 2.0 client credentials. The token request also needs the `audience` form field (the Account ID), which OAuth tooling does not always send; see `POST /v1/oauth/token`. flows: clientCredentials: tokenUrl: https://api.envoi.no/v1/oauth/token scopes: bilag:read: >- Read access to the books (the chart of accounts and journal entries). bilag:write: >- Write access to the books (the chart of accounts and journal entries). Includes bilag:read. clients:admin: Admin access to clients. Includes clients:write and clients:read. clients:read: Read access to clients. clients:write: Write access to clients. Includes clients:read. invoices:admin: >- Admin access to invoices. Includes invoices:write and invoices:read. invoices:read: Read access to invoices. invoices:write: Write access to invoices. Includes invoices:read. bearerAuth: type: http description: >- The `access_token` from `POST /v1/oauth/token`, as `Authorization: Bearer {access_token}`. It lives 15 minutes. scheme: bearer bearerFormat: JWT ````