> ## Documentation Index > Fetch the complete documentation index at: https://docs.horizonpay.co/llms.txt > Use this file to discover all available pages before exploring further. # List invoice events > Lists one invoice’s history, newest first: created, updated, finalized, emailed, viewed, downloaded, paid, voided. `invoice.viewed` and `invoice.downloaded` mean the customer opened the public link; each is recorded at most once per invoice every 10 minutes. **Scope:** `invoices:read` ## OpenAPI ````yaml /openapi.json get /invoices/{id}/events openapi: 3.1.0 info: title: Invoice-AI API version: 1.0.0 description: >- Stripe-shaped invoicing over HTTP: customers, products, prices, invoices and invoice items, with `cus_…`, `prod_…`, `price_…`, `in_…` and `ii_…` ids. - **Auth:** `Authorization: Bearer inv_live_…`, with per-key scopes. - **Envelope:** JSON bodies; responses wrap the resource in `{ "data": … }`; lists add `next_cursor`. - **Money:** integer minor units of the currency everywhere (`250000` is $2,500.00; ¥5,000 is `5000`). - **Errors:** RFC 9457 `application/problem+json` — branch on `code`. - **Idempotency:** operations that spend an invoice number, email or record payment require an `Idempotency-Key`. - **Rate limits:** 120 requests/minute per key. Sending email: 10/hour per key and 50/hour per account. See the `RateLimit-*` headers. contact: name: Invoice-AI support url: https://invoice.horizonpay.co servers: - url: https://invoice.horizonpay.co/api/v1 description: Production security: - apiKey: [] tags: - name: Business x-displayName: Business description: >- Your business profile — the issuer printed on every invoice. Read-only over the API; edit it in Settings. - name: Customers x-displayName: Customers description: >- The people and companies you bill. Every invoice references a customer by `cus_…` id. Customers are archived rather than deleted, so issued invoices keep naming who they were billed to. - name: Products x-displayName: Products description: >- The things you sell. A product carries a name and description; amounts live on its prices. Archiving sets `active: false` and keeps history intact. - name: Prices x-displayName: Prices description: >- Ways to charge for a product: an amount in integer minor units and a currency, one-time or recurring. Bill a price on an invoice line with `price: "price_…"`. - name: Invoices x-displayName: Invoices description: >- Invoices move `draft` → `open` (finalize assigns a permanent, consecutive number) → `paid`, or `open` → `void`. Drafts are freely editable and deletable; finalized invoices are frozen. `overdue` is an open invoice past its due date, derived at read time. Operations that spend a number, send email or record payment require an `Idempotency-Key`. - name: Invoice items x-displayName: Invoice items description: >- Individual lines of an invoice. Add or remove lines on a draft one at a time; totals are recomputed server-side and the whole invoice is returned. - name: Webhook endpoints x-displayName: Webhook endpoints description: >- Register https endpoints to receive invoice events (`invoice.created`, `invoice.finalized`, `invoice.paid`, …). Deliveries are signed per [Standard Webhooks](https://www.standardwebhooks.com/) with `webhook-id`, `webhook-timestamp` and `webhook-signature` headers (HMAC-SHA256 over `{id}.{timestamp}.{body}`); failed deliveries are retried with backoff. paths: /invoices/{id}/events: get: tags: - Invoices summary: List invoice events description: >- Lists one invoice’s history, newest first: created, updated, finalized, emailed, viewed, downloaded, paid, voided. `invoice.viewed` and `invoice.downloaded` mean the customer opened the public link; each is recorded at most once per invoice every 10 minutes. **Scope:** `invoices:read` operationId: listInvoiceEvents parameters: - in: path name: id schema: type: string description: The invoice, `in_…` or UUID. examples: - in_Pb2Xk7Mv4Qs9Lr1Wd6Tn3Fh8 required: true description: The invoice, `in_…` or UUID. - in: query name: cursor schema: description: >- The `next_cursor` from the previous page. Opaque — do not build it yourself. type: string description: >- The `next_cursor` from the previous page. Opaque — do not build it yourself. - in: query name: limit schema: default: 25 description: Page size, 1–100. Defaults to 25. type: integer minimum: 1 maximum: 100 description: Page size, 1–100. Defaults to 25. responses: '200': description: A page of events, newest first. headers: X-Request-Id: $ref: '#/components/headers/RequestId' RateLimit-Limit: $ref: '#/components/headers/RateLimitLimit' RateLimit-Remaining: $ref: '#/components/headers/RateLimitRemaining' RateLimit-Reset: $ref: '#/components/headers/RateLimitReset' content: application/json: example: data: - id: 9b1e5c7a-2d4f-4a86-b3e0-7c5d1f9a2e64 type: invoice.paid meta: actor: api_key request_id: req_7f3c9a1e2b4d4e8a9c6f2d1b0a3e5f71 api_key_id: 6d3a9f1c-8e2b-4c75-a0d4-1f7e3b9c5a28 reference: chk_123456 created_at: '2026-09-29T14:20:00.000Z' - id: 3e8d1a6c-5f2b-4c90-a7e3-8b4d2f1c6a95 type: invoice.viewed meta: null created_at: '2026-09-23T08:12:00.000Z' - id: 7a2c9e4f-1b6d-4f38-9e5a-2c8b6d4f1e07 type: invoice.emailed meta: to: ap@acme.example created_at: '2026-09-22T10:00:05.000Z' - id: 5c4f7b2e-9a1d-4e63-8f0b-6d3a2e9c7b18 type: invoice.finalized meta: actor: api_key request_id: req_7f3c9a1e2b4d4e8a9c6f2d1b0a3e5f71 api_key_id: 6d3a9f1c-8e2b-4c75-a0d4-1f7e3b9c5a28 created_at: '2026-09-22T10:00:00.000Z' - id: 1d9b6e3a-4c7f-4a25-b8e1-9f2c5a7d3b60 type: invoice.created meta: actor: api_key request_id: req_7f3c9a1e2b4d4e8a9c6f2d1b0a3e5f71 api_key_id: 6d3a9f1c-8e2b-4c75-a0d4-1f7e3b9c5a28 created_at: '2026-09-22T09:30:00.000Z' next_cursor: null schema: type: object properties: data: type: array items: $ref: '#/components/schemas/InvoiceEvent' description: Events, newest first. next_cursor: anyOf: - type: string - type: 'null' description: >- Pass as `cursor` to fetch the next page. `null` on the last page. examples: - MjAyNi0wOS0yMlQwOTozMDowMC4wMDBafDdmM2M required: - data - next_cursor additionalProperties: false '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: >- No such invoice. Another account's resource is also a `404`, so ids cannot be probed. Codes: `not_found`. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' examples: not_found: summary: Invoice not found. value: type: https://invoice.horizonpay.co/problems/not-found title: Not found status: 404 detail: Invoice not found. instance: req_7f3c9a1e2b4d4e8a9c6f2d1b0a3e5f71 code: not_found '422': description: >- `cursor` is not a `next_cursor` this API returned. Codes: `validation`. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' examples: validation: summary: The cursor is not valid. value: type: https://invoice.horizonpay.co/problems/validation title: Validation failed status: 422 detail: The cursor is not valid. instance: req_7f3c9a1e2b4d4e8a9c6f2d1b0a3e5f71 code: validation errors: - path: cursor message: >- Pass the `next_cursor` from the previous page, unchanged. '429': $ref: '#/components/responses/RateLimited' x-codeSamples: - lang: bash label: cURL source: >- curl https://invoice.horizonpay.co/api/v1/invoices/in_Pb2Xk7Mv4Qs9Lr1Wd6Tn3Fh8/events \ -H "Authorization: Bearer $INVOICE_AI_API_KEY" - lang: node label: Node.js source: >- import InvoiceAI from '@horizonpay/invoice-ai' const invoiceai = new InvoiceAI() // reads INVOICE_AI_API_KEY for await (const event of invoiceai.invoices.events('in_Pb2Xk7Mv4Qs9Lr1Wd6Tn3Fh8')) { console.log(event.type, event.created_at) } - lang: python label: Python source: |- from invoice_ai import InvoiceAI client = InvoiceAI() # reads INVOICE_AI_API_KEY for event in client.invoices.events("in_Pb2Xk7Mv4Qs9Lr1Wd6Tn3Fh8"): print(event.type, event.created_at) components: headers: RequestId: required: true description: >- The request id: yours, if you sent `X-Request-Id` (up to 200 characters), otherwise one we generated. Quote it to support. schema: type: string description: >- The request id: yours, if you sent `X-Request-Id` (up to 200 characters), otherwise one we generated. Quote it to support. examples: - req_7f3c9a1e2b4d4e8a9c6f2d1b0a3e5f71 RateLimitLimit: required: true description: Requests allowed in the current window for this key and bucket. schema: type: integer minimum: -9007199254740991 maximum: 9007199254740991 description: Requests allowed in the current window for this key and bucket. examples: - 120 RateLimitRemaining: required: true description: Requests left in the current window. schema: type: integer minimum: -9007199254740991 maximum: 9007199254740991 description: Requests left in the current window. examples: - 119 RateLimitReset: required: true description: Unix time (seconds) at which the window resets. schema: type: integer minimum: -9007199254740991 maximum: 9007199254740991 description: Unix time (seconds) at which the window resets. examples: - 1789371294 RetryAfter: required: true description: Seconds to wait before retrying. schema: type: integer minimum: -9007199254740991 maximum: 9007199254740991 description: Seconds to wait before retrying. examples: - 42 schemas: InvoiceEvent: type: object properties: id: type: string description: Event id (UUID). examples: - 9b1e5c7a-2d4f-4a86-b3e0-7c5d1f9a2e64 type: type: string enum: - invoice.created - invoice.updated - invoice.finalized - invoice.emailed - invoice.email_failed - invoice.viewed - invoice.downloaded - invoice.paid - invoice.voided description: >- What happened. `invoice.viewed` and `invoice.downloaded` are recorded when the customer opens the public share link, at most once per type per invoice every 10 minutes. examples: - invoice.finalized meta: anyOf: - type: object propertyNames: type: string additionalProperties: {} - type: 'null' description: >- Context: `actor`, `request_id`, `api_key_id`, and event-specific fields such as `to`, `reason` or `reference`. examples: - actor: api_key request_id: req_7f3c9a1e2b4d4e8a9c6f2d1b0a3e5f71 api_key_id: 6d3a9f1c-8e2b-4c75-a0d4-1f7e3b9c5a28 created_at: type: string description: When it happened (ISO 8601). format: date-time required: - id - type - meta - created_at additionalProperties: false description: >- One entry in an invoice’s history. The same names are used for webhook events. Problem: type: object properties: type: type: string description: >- A URI identifying the problem type: `https://invoice.horizonpay.co/problems/` with underscores as hyphens. examples: - https://invoice.horizonpay.co/problems/invalid-state title: type: string description: Short, human-readable summary of the problem type. examples: - Invalid state for this operation status: type: integer minimum: -9007199254740991 maximum: 9007199254740991 description: The HTTP status code, repeated for convenience. examples: - 409 detail: type: string description: >- Human-readable explanation of this occurrence. Wording may change — do not parse it. examples: - This invoice has been finalized and can no longer be edited. instance: type: string description: >- The request id (also sent as `X-Request-Id`), for correlating with our logs. examples: - req_7f3c9a1e2b4d4e8a9c6f2d1b0a3e5f71 code: type: string description: >- Stable machine-readable code. Branch on this, never on `detail`. One of: `validation`, `idempotency_mismatch`, `unauthorized`, `forbidden`, `not_found`, `invalid_state`, `conflict`, `idempotency_key_required`, `rate_limited`, `upstream_failed`, `internal_error`. examples: - invalid_state errors: description: Field-level problems. Present on `validation` errors only. type: array items: type: object properties: path: type: string description: Dot-path of the offending field, e.g. `items.0.unit_amount`. examples: - email message: type: string description: What is wrong with it. examples: - Enter a valid email required: - path - message additionalProperties: false required: - type - title - status - detail - instance - code additionalProperties: false description: >- An RFC 9457 problem details object, served as `application/problem+json`. Every non-2xx response uses this shape. responses: Unauthorized: description: >- The API key is missing, malformed, unknown, revoked or expired. The response carries `WWW-Authenticate: Bearer`. Codes: `unauthorized`. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' examples: unauthorized: summary: 'Send your API key as `Authorization: Bearer inv_live_…`.' value: type: https://invoice.horizonpay.co/problems/unauthorized title: Unauthorized status: 401 detail: 'Send your API key as `Authorization: Bearer inv_live_…`.' instance: req_7f3c9a1e2b4d4e8a9c6f2d1b0a3e5f71 code: unauthorized Forbidden: description: >- The key is valid but lacks a scope this operation needs (see `x-required-scope`). Codes: `forbidden`. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' examples: forbidden: summary: This credential is missing the invoices:write scope. value: type: https://invoice.horizonpay.co/problems/forbidden title: Insufficient scope status: 403 detail: This credential is missing the invoices:write scope. instance: req_7f3c9a1e2b4d4e8a9c6f2d1b0a3e5f71 code: forbidden RateLimited: description: >- Rate limit exceeded for this API key. Wait the number of seconds in `Retry-After` before retrying. Codes: `rate_limited`. headers: Retry-After: $ref: '#/components/headers/RetryAfter' X-Request-Id: $ref: '#/components/headers/RequestId' content: application/problem+json: schema: $ref: '#/components/schemas/Problem' examples: rate_limited: summary: Rate limit of 120 per 60s exceeded. value: type: https://invoice.horizonpay.co/problems/rate-limited title: Too many requests status: 429 detail: Rate limit of 120 per 60s exceeded. instance: req_7f3c9a1e2b4d4e8a9c6f2d1b0a3e5f71 code: rate_limited securitySchemes: apiKey: type: http scheme: bearer bearerFormat: inv_live__ description: >- An Invoice-AI API key sent as `Authorization: Bearer inv_live_…`. Create keys in **Settings → API keys**; the secret is shown once. Each key carries scopes, and every operation lists the scope it needs (`x-required-scope`): - `business:read` — Read your business profile, tax ID and bank details - `clients:read` — List and read your clients - `clients:write` — Create, update and archive clients - `products:read` — List and read products and prices - `products:write` — Create, update and archive products and prices - `invoices:read` — List and read invoices, including PDFs - `invoices:write` — Create, edit and delete drafts - `invoices:finalize` — Finalize invoices and void them - `invoices:send` — Email invoices to your clients - `payments:write` — Mark invoices as paid - `webhooks:manage` — Manage webhook endpoints Keys cannot be created or revoked through the API, so a leaked key cannot mint more keys. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.