Pular para o conteúdo

GET /v1/automations/{id}/runs

GET
/v1/automations/{id}/runs
curl --request GET \
--url https://seu-endereco-da-api/v1/automations/example/runs \
--header 'Authorization: Bearer <token>'

Permissão que a Chave de acesso precisa: Ler disparos automáticos (automations:read).

id
required
string
limit
number
>= 1 <= 100

How many runs to bring back (default 20, max 100)

Media typeapplication/json
object
items
required
Array<object>
object
id
required
string
firedAt
required
string format: date-time
entered
required

How many people entered the run; not a delivery count

number
skipped
required

How many were left out for already being inside another run

number
reason
required

Why the run reached nobody, when it did not

string
nullable
failed
required

How many people of this run had a message refused by Meta; people, never message count

number
failures
required

The most recent refusals of this run

Array<object>
object
messageId
required

The refused message itself, so the same person can appear twice honestly

string
contactId
required
string
nome
required
string
nullable
codigo
required

The code Meta answered with, raw

string
nullable
motivo
required

What Meta said, raw

string
nullable
quando
required
string format: date-time
failuresShown
required

How many refusals the list above can carry

number
limit
required

How many runs this page can hold, so the screen can say it is showing the latest ones

number

Example generated

{
"items": [
{
"id": "example",
"firedAt": "2026-04-15T12:00:00Z",
"entered": 1,
"skipped": 1,
"reason": "example",
"failed": 1,
"failures": [
{
"messageId": "example",
"contactId": "example",
"nome": "example",
"codigo": "example",
"motivo": "example",
"quando": "2026-04-15T12:00:00Z"
}
],
"failuresShown": 1
}
],
"limit": 1
}