Signals

A signal is an individual detected event — the raw detections that get grouped into issues. Requires a general API key with the signals:read scope.

List signals

GET /api/v1/signals

Required scope: signals:read

Query parameters

Param	Type	Notes
`appId`	string	Filter by application id.
`issueId`	string	Filter by the issue a signal was grouped into.
`limit`	integer	1–100, default 50. See pagination.
`cursor`	string	Opaque cursor from a previous `pagination.nextCursor`.

Results are ordered newest first.

Example

curl "https://guardianlogs.com/api/v1/signals?issueId=clissue001abcd00000000&limit=20" \
  -H "Authorization: Bearer $GUARDIAN_API_KEY"

{
  "data": [
    {
      "id": "clsig0001abcd000000000",
      "occurredAt": "2026-09-13T16:22:11.000Z",
      "level": "ERROR",
      "message": "Failed to process document",
      "route": "/api/process",
      "host": "app01",
      "appId": "clapp0001kidscuts000000",
      "fingerprint": "7f3a9c2e1b",
      "issueId": "clissue001abcd00000000"
    }
  ],
  "pagination": { "nextCursor": null }
}

Fields

Field	Type	Notes
`id`	string	Signal (event) id.
`occurredAt`	string (date-time)	When the event occurred.
`level`	string	`ERROR`, `WARN`, or `INFO`.
`message`	string	The log/error message.
`route`	string \	null	Route associated with the event.
`host`	string \	null	Originating host.
`appId`	string	Owning application id.
`fingerprint`	string	Grouping fingerprint.
`issueId`	string \	null	The issue this signal was grouped into, if any.

The level values here are the normalized levels stored by Guardian Logs (the level you send on ingest is mapped to one of these — see ingest.md).

See also: issues.md · pagination.md · errors.md.

Guardian Logs · guardianlogs.com · API base https://guardianlogs.com/api/v1