Skip to main content
GET
/
v1
/
alerts
curl "https://api.signa.so/v1/alerts?severity=critical&limit=50" \
  -H "Authorization: Bearer $SIGNA_API_KEY"

{
  "object": "<string>",
  "data": [
    {
      "id": "<string>",
      "object": "<string>",
      "watch_id": "<string>",
      "watch_name": "<string>",
      "trademark_id": "<string>",
      "event_type": "<string>",
      "content_version": 123,
      "must_act_by": {},
      "opposition_window_status": {},
      "severity": "<string>",
      "created_at": "<string>"
    }
  ],
  "has_more": true,
  "pagination": {},
  "request_id": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://docs.signa.so/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Returns alerts produced by any of the org’s watches. Alerts are immutable — there is no PATCH or batch state operation in monitoring v1 (VAL-API-018b). For polling clients, the recommended pattern is:
  1. Pull pages (newest first) until you encounter an id you’ve already processed.
  2. Persist alert IDs in your own store as the system of record for “open work” / “acknowledged.”
Required scope: portfolios:manage.

​
Query Parameters

​
limit
integer
default:"20"
Page size (1—100).
​
cursor
string
Opaque cursor from the previous response.
​
severity
string
Filter by normal, high, or critical.
​
event_type
string
Filter by trademark.created, trademark.updated, trademark.status_changed, trademark.retracted, or trademark.corrected.
The legacy ?after= and ?after_seq= parameters are explicitly rejected with 400. Migrate to opaque cursor pagination.

​
Response

​
object
string
Always "list".
​
data
object[]
Array of Alert objects.
​
has_more
boolean
Whether more pages exist.
​
pagination
object
Cursor envelope.
​
request_id
string
Request identifier.
curl "https://api.signa.so/v1/alerts?severity=critical&limit=50" \
  -H "Authorization: Bearer $SIGNA_API_KEY"