GET /audit-logs

Internal API (/api/v1), dashboard JWT (Authorization: Bearer ...). Provider users need the sp_admin staff role (or the provider’s own admin account); other staff roles, customers, technicians and building owners get 403. Row-level security then enforces isolation: provider users only ever see their own provider’s entries (any provider_id filter they pass is ignored); operators (admin) see everything and may filter by provider_id.

Endpoint

GET /api/v1/audit-logs

Query parameters

Parameter	Type	Required	Description
`limit`	int	No	1–500, default 100
`offset`	int	No	Default 0
`start_time`	ISO datetime	No	Filter `created_at >=`
`end_time`	ISO datetime	No	Filter `created_at <=`
`provider_id`	UUID	No	Admin only — filter to one provider
`resource_type`	string	No	e.g. `user`, `subscription`
`resource_id`	string	No	Single resource id
`resource_ids`	string	No	Comma-separated ids (rollup, e.g. a subscriber + its subscriptions)

Typical use: the per-record History view — pass resource_type + resource_id (or resource_ids for a rollup) plus an optional time range.

Response — 200 OK

Returns an array of audit entries (newest first):

[
  {
    "id": "uuid",
    "created_at": "2026-06-30T12:00:00Z",
    "actor_user_id": "uuid",
    "actor_email": "string",
    "actor_role": "service_provider",
    "action": "provider.user.invite",
    "provider_id": "uuid",
    "resource_type": "user",
    "resource_id": "uuid",
    "metadata": {}
  }
]

Errors

Status	Meaning
`401`	`Bearer token required` — missing or malformed `Authorization` header

Query-layer failures degrade to an empty array with 200 rather than a 5xx — an empty result is not proof of an empty log.

Overview

Plan Discovery

Provisioning

Reports

Checkout Utilities

Subscribers & Subscriptions

AI Support Agent

Provider Operations (Internal API)

Endpoint

Query parameters

Response — 200 OK

Errors

​Endpoint

​Query parameters

​Response — 200 OK

​Errors

Endpoint

Query parameters

Response — 200 OK

Errors