Skip to Content
SendlySendly
API ReferenceEvents

List event names

GET
/api/v1/events/names

Every distinct event name in the project, most frequent first — the vocabulary a caller needs before filtering events or pointing a workflow trigger at one. Unpaginated: the set is bounded by what the integration emits, not by event volume.

Requires the events:read scope — View the custom events your application has recorded.

headerAuthorizationBearer <API Key>

API key authentication. Use a sk_* (FULL) or pk_* (SENDING_ONLY) key as the bearer token. Public keys (pk_*) are restricted to the email-send endpoints and the self-serve list subscribe/unsubscribe pair; every other endpoint — event tracking included — answers 403 for them. In scope terms (used by /api/v1/* operations): FULL keys hold every scope; SENDING_ONLY keys hold only emails:send.

Response Body

Event names

application/json
  1. response

Every distinct event name in the project, most frequent first.

data*array<string>
Example Request
curl -X GET 'https://api.sendly.now/api/v1/events/names'
Example Response
{  "data": [    "string"  ]}