List event names

GET/api/v1/contact-events/names

Requires anorganization API keywith the scopeautomations:read

The event names an automation can use: Mailyte's own (built_in, always listed), then every name your systems have sent in the window, most recently seen first, up to 100. This is what the automation builder's event list is made from, so a name appears there as soon as the first event carrying it is received — historical ones included.

Parameters

Name	In	Type	Description
`days`	query	integer	How far back to look, 1 to 365. Default 90, which is also how long events are kept.

Request

GET/api/v1/contact-events/names

curl -X GET 'https://app.mailyte.com/api/v1/contact-events/names' \
  -H 'Authorization: Bearer mk_live_YOUR_API_KEY'

const response = await fetch('https://app.mailyte.com/api/v1/contact-events/names', {
  method: 'GET',
  headers: {
    Authorization: 'Bearer mk_live_YOUR_API_KEY',
  },
});
const { data } = await response.json();

import requests
response = requests.get(
    "https://app.mailyte.com/api/v1/contact-events/names",
    headers={"Authorization": "Bearer mk_live_YOUR_API_KEY"},
)
data = response.json()["data"]

<?php

$response = Http::withToken('mk_live_YOUR_API_KEY')
    ->get('https://app.mailyte.com/api/v1/contact-events/names');

$data = $response->json('data');

require "net/http"
require "json"
uri = URI("https://app.mailyte.com/api/v1/contact-events/names")
request = Net::HTTP::Get.new(uri)
request["Authorization"] = "Bearer mk_live_YOUR_API_KEY"
response = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |http| http.request(request) }

The key names its own organization, so no X-Organization-ID header is needed.

Response

Success.

dataarray<object>
- namestring
  The event name, e.g. order_completed, or a built-in one like email.clicked.
- built_inboolean
  Raised by Mailyte itself rather than sent by your systems; always available.
- countinteger
  How many have been received, over the window asked for. 0 for a built-in name nobody has triggered yet.
- last_seen_atstring

Returned inside the standard envelope.

Errors

Status	When
`401`	The API key is missing, unknown, revoked or expired. All four answer identically, on purpose: distinguishing them would confirm which keys exist.
`403`	The key is valid but may not do this: it lacks the required scope, its IP allowlist does not include you, or this endpoint does not accept API keys.
`404`	No such resource in this organization.
`422`	The request was understood but the values were not acceptable.
`429`	Too many requests, or the organization has spent its sending allowance. `Retry-After` says how long to wait.

Every status, with what causes it and what to do, is on the error reference.