# List the standard event names

Source: https://kirora.io/docs/api/reference/listStandardEventNames

`GET /v1/events/standard-names`

Requires an API key with the `events:read` scope. [About keys and scopes](https://kirora.io/docs/api/reference/authentication)

Works with integration, agent and partner keys. Also available to embed sessions.

Kirora's standard names the workspace has neither sent nor defined, with what each means: Segment's e-commerce names (`commerce`) and its B2B SaaS names (`saas`). Offered beside the catalogue in pickers; once sent or defined, a name moves to the catalogue. Commerce names drive revenue: `Order Completed` with `total` and `currency`.

## Header parameters

- `Kirora-Workspace` (string, optional, pattern `^[A-Za-z0-9._:-]{1,128}$`) — Partner keys only: the child workspace to act in, by the external id the partner gave it. Without it, a partner key acts in its own workspace. Any other key that sends it is refused with 403, and an unknown workspace is 404.

## Returns

Returns `200 OK` with a list of `StandardEventName` objects in `data`. Otherwise returns an error; [Errors](https://kirora.io/docs/api/reference/errors) lists every code and which to retry.

- `name` (string, required)
- `category` (string, required, one of `commerce`, `saas`) — `commerce`: a shop; `saas`: a product people sign up to.
- `description` (string, required) — What the name means, as its Segment spec defines it.

## Example

```bash
curl https://api.kirora.io/v1/events/standard-names \
  -H "Authorization: Bearer $KIRORA_API_KEY"
```

Response `200`:

```json
{
  "data": [
    {
      "name": "Trial Started",
      "category": "saas",
      "description": "A contact began a free trial."
    },
    {
      "name": "Checkout Started",
      "category": "commerce",
      "description": "A contact began checking out, with the products in products[]."
    }
  ]
}
```