---
title: "List recurring invoice activity"
method: GET
path: "/companies/{company}/recurring-invoices/{recurring_invoice}/activities"
tags: ["Recurring Invoices"]
---

# List recurring invoice activity

`GET /companies/{company}/recurring-invoices/{recurring_invoice}/activities`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/recurring-invoices/{recurring_invoice}/activities`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Return the cursor-paginated activity timeline (domain events: activation, pause, resume, generation, failure, cancellation, etc.) for a recurring invoice. Metadata is sanitized to never expose internal identifiers.

## Path parameters

- `company` string, uuid, required
- `recurring_invoice` string, uuid, required

## Query parameters

- `limit` integer
- `starting_after` string
- `ending_before` string

## Headers

- `Factuarea-Version` string, date

## Response `200`

- object: Cursor-paginated list envelope shared by every v1 listing endpoint. `data` holds the page items; `has_more` signals whether another page exists; `next_cursor` is the cursor to pass back for the following page. Treat it as strictly opaque: send it through verbatim, never parse it and never assume a format — it is not the same across listings, and each listing documents its own cursor parameter. Concrete listings narrow `data` to their resource type via `allOf`.
  - `data` object[], required: Items on the current page.
    - `object` 'activity', required
    - `event_type` string, required: Domain event type (e.g. `recurring_invoice.activated`, `recurring_invoice.executed`, `recurring_invoice.cancelled`).
    - `description` string, required: Human-readable description of the event in Spanish.
    - `metadata` object, required: Event metadata. Internal identifiers (PKs) are stripped; `*_uuid` values are preserved.
    - `performed_by` object, nullable, required: Actor that originated the event. `{type:"user",...}` for an internal user, `{type:"api_key",...}` when performed via the public v1 API, or `null` when the event is system-generated (scheduler, periodic sweep) with no attributable actor.
      - `type` 'user' | 'api_key', required: Type of actor that originated the event: `user` for a human in the internal app, `api_key` for an action performed through the public v1 API.
      - `id` string, required: UUID v7 of the actor: the user when `type=user`, or the API key when `type=api_key`.
      - `name` string, nullable, required: Actor name at the time of the event: the user name or the API key name. `null` if it could not be resolved.
    - `created_at` string, date-time, required: When the event occurred (ISO 8601).
  - `has_more` boolean, required: Whether more pages are available after this one.
  - `next_cursor` string, nullable, required: Opaque cursor for the next page, or `null` when `has_more` is `false`. The example below shows the shape used by most listings; others return a different one, so pass the value back verbatim instead of validating it.

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company.
- `422`: Validation failed, or the recurring invoice cannot undergo the requested state transition (e.g. resuming a recurrence that is not paused). The `error.param` field identifies which input is invalid, if any.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)