Error

A valid request URL is required to generate request examples

{
  "success": true,
  "data": [
    {
      "id": "act_88f1",
      "kind": "audit",
      "action": "PUT /agents/:id/guardrails",
      "route": "/agents/:id/guardrails",
      "method": "PUT",
      "status": 200,
      "actorType": "user",
      "actorId": "user_2abc",
      "isFlowyteStaff": false,
      "tsMs": 1752330000000
    },
    {
      "id": "act_88f2",
      "kind": "staff_access",
      "event": "session_start",
      "actorType": "staff",
      "staffEmail": "support@flowyte.com",
      "reason": "ticket #4821 — customer-reported call drop",
      "reasonType": "support_ticket",
      "isFlowyteStaff": true,
      "tsMs": 1752326400000
    }
  ],
  "pagination": {
    "page": 1,
    "limit": 20,
    "total": 2,
    "totalPages": 1
  }
}

{
  "type": "about:blank",
  "title": "<string>",
  "status": 123,
  "detail": "<string>",
  "instance": "<string>",
  "code": "<string>",
  "errors": [
    {
      "field": "<string>",
      "message": "<string>"
    }
  ]
}

{
  "type": "about:blank",
  "title": "<string>",
  "status": 123,
  "detail": "<string>",
  "instance": "<string>",
  "code": "<string>",
  "errors": [
    {
      "field": "<string>",
      "message": "<string>"
    }
  ]
}

Observe

The org's Settings→Activity trail (what any user — and Flowyte staff — did)

The customer-facing account ACTIVITY trail: a unified, newest-first timeline of what happened in the org — the org's own mutations (audit_logs) merged with the customer-visible Flowyte-STAFF access ledger (staff_access_log). Flowyte-staff access/action rows carry isFlowyteStaff=true (+ staffEmail, reason) so the UI can highlight them ("Flowyte staff accessed your account on <date> — reason <ticket>"). Org-scoped (RLS): a customer sees only their OWN org. VALUE-FREE — route/verb/status/reason only, never request bodies or PII. Use this for the human-readable Settings→Activity view (it includes Flowyte-staff access rows). For a raw, machine-oriented forensic export of API/key events filtered by date range and actor type, use listAuditLogs instead.

GET

activity

Error

A valid request URL is required to generate request examples

{
  "success": true,
  "data": [
    {
      "id": "act_88f1",
      "kind": "audit",
      "action": "PUT /agents/:id/guardrails",
      "route": "/agents/:id/guardrails",
      "method": "PUT",
      "status": 200,
      "actorType": "user",
      "actorId": "user_2abc",
      "isFlowyteStaff": false,
      "tsMs": 1752330000000
    },
    {
      "id": "act_88f2",
      "kind": "staff_access",
      "event": "session_start",
      "actorType": "staff",
      "staffEmail": "support@flowyte.com",
      "reason": "ticket #4821 — customer-reported call drop",
      "reasonType": "support_ticket",
      "isFlowyteStaff": true,
      "tsMs": 1752326400000
    }
  ],
  "pagination": {
    "page": 1,
    "limit": 20,
    "total": 2,
    "totalPages": 1
  }
}

{
  "type": "about:blank",
  "title": "<string>",
  "status": 123,
  "detail": "<string>",
  "instance": "<string>",
  "code": "<string>",
  "errors": [
    {
      "field": "<string>",
      "message": "<string>"
    }
  ]
}

{
  "type": "about:blank",
  "title": "<string>",
  "status": 123,
  "detail": "<string>",
  "instance": "<string>",
  "code": "<string>",
  "errors": [
    {
      "field": "<string>",
      "message": "<string>"
    }
  ]
}

Authorizations

Authorization

string

header

required

Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.

Query Parameters

page

integer

default:1

1-based page number for offset pagination. Defaults to 1 (the first page).

Required range: x >= 1

limit

integer

default:20

Page size — how many items to return per page (1–100). Defaults to 20.

Required range: 1 <= x <= 100

Response

Paginated org-activity timeline (newest first).

success

boolean

required

data

object[]

required

Show child attributes

pagination

object

required

Show child attributes

message

string

errors

object[]

Show child attributes

Delete a dashboard List scheduled reports

Using the API

Endpoints

The org's Settings→Activity trail (what any user — and Flowyte staff — did)

Authorizations

Query Parameters

Response