POST /v1/automations/panorama
const url = 'https://seu-endereco-da-api/v1/automations/panorama';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"filter":{},"dia":"example","disparoId":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://seu-endereco-da-api/v1/automations/panorama \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "filter": {}, "dia": "example", "disparoId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" }'Permissão que a Chave de acesso precisa: Ler disparos automáticos (automations:read).
Authorizations
Seção intitulada “Authorizations”Request Bodyrequired
Seção intitulada “Request Bodyrequired”object
object
Example generated
{ "filter": {}, "dia": "example", "disparoId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0"}Responses
Seção intitulada “Responses”object
How many automations are switched on, cut or not
Sends inside the cut. It counts sends, not heads: one person reached on two days, or by two automations, is counted twice
How many different people the cut reaches, each counted once
What those sends cost, in micros, tariff plus markup, as the wallet would be charged
Sends no tariff covers, left out of the cost; it is our price list that is missing, not their balance
The channel wallet balance in micros, so the screen can say how much of it the week eats
The same count over the seven days before today
One entry per day ahead, seven of them; the chosen day does not empty the others
object
The local day, as yyyy-MM-dd
How many sends the cut makes on that day
How many sends the same cut made on the matching day of the week before
Every switched-on automation, biggest first, even the ones the cut leaves out
object
Sends this automation makes inside the cut, so a row can be clicked to narrow the screen
Who receives, by tag and by gender, counted over the sends of the cut
object
Etiqueta, sexo, signo, canal, mes_de_aniversario, consentimento, or campo:
False when the platform field behind it is off; then the screen teaches instead of showing zero
Why it is unavailable
The contact field to turn on, when there is one
True when one contact can land on several values, so the shares add up past the whole
object
What the screen sends back as a cut condition
What the person reads
Share of the current total, from 0 to 1, so a number says size and not only amount
The tag colour, when the value has one
The condition that isolates this row, so the screen cuts by exactly what was counted. Null when the axis has no equivalent in the contact filter, which today is only the channel axis
object
The contact filter field this row cuts by
The operator the contact filter dialect accepts for that field
The value the operator carries
object
When this count was taken, so nobody trusts a dead number
Example generated
{ "ligados": 1, "envios": 1, "pessoas": 1, "custoMicros": 1, "enviosSemTarifa": 1, "saldoMicros": 1, "semanaAnterior": 1, "dias": [ { "dia": "example", "total": 1, "anterior": 1 } ], "porDisparo": [ { "id": "example", "nome": "example", "envios": 1 } ], "eixos": [ { "chave": "example", "rotulo": "example", "disponivel": true, "motivo": "example", "campoKey": "example", "multivalor": true, "valores": [ { "valor": "example", "rotulo": "example", "total": 1, "fatia": 1, "cor": "example", "recorte": { "field": "example", "op": "example", "value": {} } } ] } ], "apuradoEm": "2026-04-15T12:00:00Z"}