Tags and notes

Tags and notes help your team organize a case. A tag is a colored label you define once and attach to as many entities as you like. A note is a short piece of free text written on one entity.

Both work on the same four kinds of entity:

Tags

Create a tag

POST /v1/tags/ with a name (trimmed, 1 to 50 characters, unique in your organization) and an optional color (a #rrggbb hex string, default #6c757d).

curl -X POST "https://monitoring.seqlense.com/api/v1/tags/" \
  -H "Authorization: Bearer sq_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "High risk", "color": "#dc3545" }'

{ "id": "3f2a1b0c-9d8e-4f7a-8b6c-5d4e3f2a1b0c" }

A duplicate name returns 400 {"error": "Tag already exists or creation failed"}.

List, rename, delete

Attach and detach

POST /v1/tags/attach and POST /v1/tags/detach take the same body: a tag_id from your organization plus the entity. Both return {"ok": true}, and both are safe to repeat: attaching a tag twice keeps one link, detaching a tag that is not there does nothing.

curl -X POST "https://monitoring.seqlense.com/api/v1/tags/attach" \
  -H "Authorization: Bearer sq_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tag_id": "3f2a1b0c-9d8e-4f7a-8b6c-5d4e3f2a1b0c",
    "entity_type": "OB_CLIENT",
    "entity_id": "POSTG0000114"
  }'

A tag_id that is not one of your tags returns 400 {"error": "Tag not found"}.

Read the tags on an entity

curl -H "Authorization: Bearer sq_YOUR_API_KEY" \
  "https://monitoring.seqlense.com/api/v1/tags/entity?entity_type=IDENTITY&entity_id=6f9619ff-8b86-4d11-b42d-00c04fc964ff"

{
  "tags": [
    { "tag_id": "3f2a1b0c-9d8e-4f7a-8b6c-5d4e3f2a1b0c", "name": "High risk", "color": "#dc3545" }
  ]
}

When you merge two identities, the source's tags move to the target.

Notes

Notes are investigation notes: why an alert was closed, what a client said on the phone, which other account is the same person. The notes you see on an alert in the dashboard are the same notes as entity_type=ALERT here.

Add a note

POST /v1/notes/ with entity_type, entity_id and text. The text is trimmed and must be 1 to 4000 characters (counted in bytes, so accented characters count more than once).

curl -X POST "https://monitoring.seqlense.com/api/v1/notes/" \
  -H "Authorization: Bearer sq_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "entity_type": "IDENTITY",
    "entity_id": "6f9619ff-8b86-4d11-b42d-00c04fc964ff",
    "text": "Same person as the order-book client POSTG0000114."
  }'

{ "id": "1c2d3e4f-5a6b-4c7d-8e9f-0a1b2c3d4e5f" }

Adding a note is recorded in the activity feed (UPDATE, "Note added"); for an identity it shows up in GET /v1/identity/activity.

List notes

GET /v1/notes/?entity_type=…&entity_id=… returns every note on that entity, newest first. Not paginated.

{
  "notes": [
    {
      "id": "1c2d3e4f-5a6b-4c7d-8e9f-0a1b2c3d4e5f",
      "text": "Same person as the order-book client POSTG0000114.",
      "created_by": 17,
      "created_by_name": "Jane Doe",
      "created_at": "2026-07-27 10:00:00"
    }
  ]
}

created_by is the author's user id, 0 for a note written with an API key. created_by_name is Unknown when the account no longer exists.

Delete a note

DELETE /v1/notes/?id=… permanently deletes a note and returns {"ok": true}. An id that does not exist in your organization returns 404. Notes cannot be edited: delete and write a new one.

Limits at a glance

Full reference

Every endpoint, parameter and schema is in the API Reference.