Conversations and service requests

Paginated list of conversations, with filters that can be combined (all of them are joined with AND). With no filter at all, it returns every conversation, from newest to oldest.

Permission: Look up conversations.

Dates accept ISO 8601 (2026-10-01T08:00:00-03:00), YYYY-MM-DD or YYYY-MM-DD HH:MM:SS; without a time zone, they are read in the server time zone. A date that makes no sense: 400 data_invalida with campo.

# department 2 queue right now, longest waiting first
curl -s "https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/listar&estado=fila&departamento_id=2&ordem=antigas" \
  -H "Authorization: Bearer $CHATISP_CHAVE"

# closed yesterday with tag 3, page 2
curl -s "https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/listar&estado=encerrada&etiqueta_id=3&encerradas_desde=2026-09-30&criadas_ate=2026-09-30&pagina=2" \
  -H "Authorization: Bearer $CHATISP_CHAVE"

<?php
// walks through every page of open conversations
$pagina = 1;
do {
    $url = 'https://atendimento.seuprovedor.com.br/api_publica.php?' . http_build_query([
        'r' => 'conversas/listar', 'abertas' => 1, 'limite' => 100, 'pagina' => $pagina,
    ]);
    $ch = curl_init($url);
    curl_setopt_array($ch, [
        CURLOPT_RETURNTRANSFER => true,
        CURLOPT_HTTPHEADER     => ['Authorization: Bearer ' . getenv('CHATISP_CHAVE')],
    ]);
    $r = json_decode(curl_exec($ch), true);
    curl_close($ch);
    foreach ($r['conversas'] as $c) {
        echo $c['protocolo'], ' ', $c['estado'], ' ', $c['atendente'], PHP_EOL;
    }
    $pagina++;
} while ($pagina <= $r['paginacao']['paginas']);

import os, requests

r = requests.get("https://atendimento.seuprovedor.com.br/api_publica.php", params={
    "r": "conversas/listar",
    "estado": "fila,humano",
    "atendente_id": 7,
    "limite": 100,
}, headers={"Authorization": "Bearer " + os.environ["CHATISP_CHAVE"]}, timeout=30)

dados = r.json()
print(dados["paginacao"]["total"], "conversations with agent 7")
for c in dados["conversas"]:
    print(c["protocolo"], c["nome"], c["nao_lidas"])

{
  "ok": true,
  "conversas": [
    {
      "id": 18360,
      "protocolo": "20261001-0055",
      "conexao_id": 1,
      "telefone": "5544988887777",
      "nome": "João Pereira",
      "estado": "fila",
      "aguardando_cliente": false,
      "departamento_id": 2,
      "departamento": "Billing",
      "atendente_id": null,
      "atendente": "",
      "nao_lidas": 2,
      "motivo_encerramento": "",
      "resumo": null,
      "criada_em": "2026-10-01T10:31:08-03:00",
      "ultima_mensagem_em": "2026-10-01T10:31:40-03:00",
      "encerrada_em": null
    }
  ],
  "paginacao": { "pagina": 1, "limite": 50, "total": 1, "paginas": 1 }
}

Route-specific errors: parametro_invalido (state, order, limit or page outside the accepted values, with campo), data_invalida, telefone_invalido.

Returns a full conversation (with tags) and its latest messages, in chronological order. Use it to show the progress of a protocol number in the CRM, to check whether the customer replied to a notice or to fetch the context after a webhook.

Permission: Look up conversations.

With more than one identifier, the first one in the order conversa_id/id, protocolo, telefone wins. For more than 100 messages, or to paginate the history, use conversas/mensagens.

# by protocol number, with the 3 latest messages
curl -s "https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/consultar&protocolo=20261001-0042&mensagens=3" \
  -H "Authorization: Bearer $CHATISP_CHAVE"

# the most recent conversation of a phone number, without messages
curl -s "https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/consultar&telefone=44999990000&mensagens=0" \
  -H "Authorization: Bearer $CHATISP_CHAVE"

<?php
$url = 'https://atendimento.seuprovedor.com.br/api_publica.php?' . http_build_query([
    'r' => 'conversas/consultar', 'protocolo' => '20261001-0042', 'mensagens' => 3,
]);
$ch = curl_init($url);
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => ['Authorization: Bearer ' . getenv('CHATISP_CHAVE')],
]);
$r = json_decode(curl_exec($ch), true);
curl_close($ch);

echo $r['conversa']['estado'], ' with ', $r['conversa']['atendente'] ?: 'nobody', PHP_EOL;
foreach ($r['mensagens'] as $m) {
    echo $m['criada_em'], ' [', $m['autor'], '] ', $m['conteudo'] ?: ($m['transcricao'] ?? ''), PHP_EOL;
}

import os, requests

r = requests.get("https://atendimento.seuprovedor.com.br/api_publica.php", params={
    "r": "conversas/consultar", "protocolo": "20261001-0042", "mensagens": 3,
}, headers={"Authorization": "Bearer " + os.environ["CHATISP_CHAVE"]}, timeout=30)

if r.status_code == 404:
    print("Protocol number does not exist")
else:
    for m in r.json()["mensagens"]:
        print(m["criada_em"], m["autor"], m["conteudo"])

{
  "ok": true,
  "conversa": {
    "id": 18342,
    "protocolo": "20261001-0042",
    "conexao_id": 1,
    "telefone": "5544999990000",
    "nome": "Maria Souza",
    "estado": "humano",
    "aguardando_cliente": false,
    "departamento_id": 1,
    "departamento": "Technical support",
    "atendente_id": 7,
    "atendente": "Carlos Lima",
    "nao_lidas": 0,
    "motivo_encerramento": "",
    "resumo": null,
    "criada_em": "2026-10-01T09:12:40-03:00",
    "ultima_mensagem_em": "2026-10-01T09:20:03-03:00",
    "encerrada_em": null,
    "etiquetas": []
  },
  "mensagens": [
    {
      "id": 402850, "conversa_id": 18342, "direcao": "recebida", "autor": "cliente", "autor_nome": "",
      "tipo": "texto", "conteudo": "My internet has been down since early this morning", "transcricao": null, "arquivo": null,
      "status": "entregue", "erro": null, "responde_a": null, "editada": false, "apagada": false,
      "criada_em": "2026-10-01T09:12:40-03:00"
    },
    {
      "id": 402852, "conversa_id": 18342, "direcao": "enviada", "autor": "ia", "autor_nome": "",
      "tipo": "texto", "conteudo": "Hi, Maria! I will check your connection right now.", "transcricao": null, "arquivo": null,
      "status": "lida", "erro": null, "responde_a": null, "editada": false, "apagada": false,
      "criada_em": "2026-10-01T09:12:52-03:00"
    },
    {
      "id": 402866, "conversa_id": 18342, "direcao": "enviada", "autor": "atendente", "autor_nome": "Carlos Lima",
      "tipo": "texto", "conteudo": "Maria, I found the problem. A technician will visit you this afternoon.", "transcricao": null, "arquivo": null,
      "status": "entregue", "erro": null, "responde_a": 402850, "editada": false, "apagada": false,
      "criada_em": "2026-10-01T09:20:03-03:00"
    }
  ]
}

Route-specific errors: identificador_obrigatorio (none of the three identifiers), telefone_invalido, nao_encontrado (404: id or protocol number not found, or phone number with no conversation).

Walks through the whole history of a conversation, in pages, using a message id cursor. Unlike numbered pagination, the cursor neither skips nor repeats messages when new messages arrive in the middle of the reading. Messages always come in chronological order (oldest to newest) and without internal notes.

Permission: Look up conversations.

Two ways to use it

• Read everything backwards (export the history): first call without a cursor (the newest messages); while tem_mais is true, call again with antes_de set to cursor.antes_de.
• Follow what arrives (mirror the conversation in your system): store cursor.depois_de and, next time, call with depois_de; while tem_mais is true, continue with the new cursor.depois_de.

# the 50 most recent
curl -s "https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/mensagens&conversa_id=18342" \
  -H "Authorization: Bearer $CHATISP_CHAVE"

# the previous page
curl -s "https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/mensagens&conversa_id=18342&antes_de=402850" \
  -H "Authorization: Bearer $CHATISP_CHAVE"

# what arrived after message 402866
curl -s "https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/mensagens&protocolo=20261001-0042&depois_de=402866" \
  -H "Authorization: Bearer $CHATISP_CHAVE"

<?php
// exports the full history, from oldest to newest
function chatisp(array $params): array {
    $ch = curl_init('https://atendimento.seuprovedor.com.br/api_publica.php?' . http_build_query($params));
    curl_setopt_array($ch, [
        CURLOPT_RETURNTRANSFER => true,
        CURLOPT_HTTPHEADER     => ['Authorization: Bearer ' . getenv('CHATISP_CHAVE')],
    ]);
    $r = json_decode(curl_exec($ch), true);
    curl_close($ch);
    return $r;
}

$historico = [];
$params = ['r' => 'conversas/mensagens', 'conversa_id' => 18342, 'limite' => 100];
do {
    $r = chatisp($params);
    $historico = array_merge($r['mensagens'], $historico);
    $params['antes_de'] = $r['cursor']['antes_de'];
} while ($r['tem_mais']);

import os, requests

URL = "https://atendimento.seuprovedor.com.br/api_publica.php"
CAB = {"Authorization": "Bearer " + os.environ["CHATISP_CHAVE"]}

def novas_mensagens(conversa_id, ultimo_id):
    """Fetches everything that arrived after ultimo_id and returns the new cursor."""
    while True:
        r = requests.get(URL, headers=CAB, timeout=30, params={
            "r": "conversas/mensagens", "conversa_id": conversa_id,
            "depois_de": ultimo_id, "limite": 100}).json()
        for m in r["mensagens"]:
            print(m["autor"], m["conteudo"])
        ultimo_id = r["cursor"]["depois_de"]
        if not r["tem_mais"]:
            return ultimo_id

{
  "ok": true,
  "conversa_id": 18342,
  "mensagens": [
    { "id": 402852, "conversa_id": 18342, "direcao": "enviada", "autor": "ia", "...": "..." },
    { "id": 402866, "conversa_id": 18342, "direcao": "enviada", "autor": "atendente", "...": "..." }
  ],
  "tem_mais": true,
  "cursor": { "antes_de": 402852, "depois_de": 402866 }
}

Route-specific errors: identificador_obrigatorio, nao_encontrado, parametro_invalido (limite outside 1 to 100, with maximo; a cursor that is not an integer).

Moves an open conversation to a department, to an agent or to both, exactly like the Transfer button in the panel. Examples: the ERP detects that the customer is past due and sends the conversation to Billing; the CRM routes business customers to their account manager.

Permission: Manage conversations.

What happens

• In every case the conversation leaves automation: if it was with the AI or in a flow, they stop replying.
• Sharing of the conversation with other agents is undone; the recipient decides who to share it with.
• The API does not check whether the agent belongs to the department: the combination is the integration's responsibility.
• The customer gets no message about the transfer. The only possible exception is the Waiting time notice, when it is turned on in Settings and the conversation enters the queue with every agent busy.
• The conversa_transferida webhook fires (and conversa_atribuida when automatic distribution delivers the conversation to someone).

curl -s -X POST "https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/transferir" \
  -H "Authorization: Bearer $CHATISP_CHAVE" \
  -H "Content-Type: application/json" \
  -d '{"protocolo": "20261001-0042", "departamento_id": 2, "motivo": "customer past due"}'

<?php
$ch = curl_init('https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/transferir');
curl_setopt_array($ch, [
    CURLOPT_POST           => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => ['Authorization: Bearer ' . getenv('CHATISP_CHAVE'), 'Content-Type: application/json'],
    CURLOPT_POSTFIELDS     => json_encode(['conversa_id' => 18342, 'atendente_id' => 7, 'motivo' => 'business customer']),
]);
$r = json_decode(curl_exec($ch), true);
curl_close($ch);
echo $r['conversa']['estado'], ' with ', $r['conversa']['atendente'], PHP_EOL;

import os, requests

r = requests.post("https://atendimento.seuprovedor.com.br/api_publica.php",
    params={"r": "conversas/transferir"},
    headers={"Authorization": "Bearer " + os.environ["CHATISP_CHAVE"]},
    json={"conversa_id": 18342, "departamento_id": 2, "atendente_id": 9},
    timeout=30)
print(r.status_code, r.json()["conversa"]["estado"])

The response returns the conversation already updated, with tags:

{
  "ok": true,
  "conversa": {
    "id": 18342,
    "protocolo": "20261001-0042",
    "estado": "fila",
    "departamento_id": 2,
    "departamento": "Billing",
    "atendente_id": null,
    "atendente": "",
    "...": "other fields of the conversation object",
    "etiquetas": []
  }
}

If automatic distribution delivers the conversation right away, estado already comes back as humano, with the agent it picked.

Route-specific errors: parametro_obrigatorio (no department and no agent; campo set to departamento_id|atendente_id), departamento_invalido, atendente_invalido (not found, inactive or deleted), conversa_encerrada (409), identificador_obrigatorio, nao_encontrado.

Closes an open conversation, like the End button in the panel. Example: the work order system closes the work order and closes the WhatsApp request with the right reason.

Permission: Manage conversations.

What happens to the customer

With enviar_mensagem true (default), closing through the API does the same as closing through the panel:

1. Closed ticket message: the text configured in Settings (with {protocolo} and {nome} filled in) is sent, as long as there was real service: the customer took part in the conversation, or the AI or an agent talked to them. With the field empty in Settings, nothing is sent.
2. Satisfaction survey: if Send the survey when closing handled conversations is on (see Satisfaction survey), the question is sent when the AI or an agent replied to the customer in the conversation. The score the customer gives goes into the reports.

With enviar_mensagem=false, neither of them is sent. Use it, for example, when closing old or test conversations in bulk.

What happens behind the scenes

• The state becomes encerrada, with the reason; the conversation leaves the flow and the AI; an open reply wait is ended.
• If the customer wrote something, the AI writes the request resumo in the background (look up the conversation again a few minutes later).
• Service orders opened from this request have their summary rewritten to cover the whole conversation.
• The conversa_encerrada webhook fires, with motivo set to the name of the chosen reason (or to the key identification, without a reason).

# closes with a reason, sending the closing message and the survey
curl -s -X POST "https://atendimento.seuprovedor.com.br/api_publica.php" \
  -H "Authorization: Bearer $CHATISP_CHAVE" \
  -d "r=conversas/encerrar" -d "protocolo=20261001-0042" -d "motivo_id=1"

# closes silently
curl -s -X POST "https://atendimento.seuprovedor.com.br/api_publica.php" \
  -H "Authorization: Bearer $CHATISP_CHAVE" \
  -d "r=conversas/encerrar" -d "conversa_id=18342" -d "enviar_mensagem=0"

<?php
$ch = curl_init('https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/encerrar');
curl_setopt_array($ch, [
    CURLOPT_POST           => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => ['Authorization: Bearer ' . getenv('CHATISP_CHAVE'), 'Content-Type: application/json'],
    CURLOPT_POSTFIELDS     => json_encode(['protocolo' => '20261001-0042', 'motivo_id' => 1]),
]);
$r = json_decode(curl_exec($ch), true);
$status = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
if ($status === 409) {
    // conversa_encerrada: it was already closed; treat it as success
}

import os, requests

r = requests.post("https://atendimento.seuprovedor.com.br/api_publica.php",
    params={"r": "conversas/encerrar"},
    headers={"Authorization": "Bearer " + os.environ["CHATISP_CHAVE"]},
    json={"conversa_id": 18342, "motivo_id": 1, "enviar_mensagem": False},
    timeout=30)
c = r.json()["conversa"]
print(c["estado"], c["motivo_encerramento"], c["encerrada_em"])

{
  "ok": true,
  "conversa": {
    "id": 18342,
    "protocolo": "20261001-0042",
    "estado": "encerrada",
    "motivo_encerramento": "Resolved",
    "resumo": null,
    "encerrada_em": "2026-10-01T11:05:12-03:00",
    "...": "other fields of the conversation object"
  }
}

Route-specific errors: motivo_invalido (not found or inactive), conversa_encerrada (409: it was already closed; when reprocessing, treat it as success), parametro_invalido (enviar_mensagem with a value that is not boolean), identificador_obrigatorio, nao_encontrado.

Changes the tags of a conversation (open or closed). Tags are registered in Catalogs and listed by etiquetas/listar. Examples: tag VIP when the ERP identifies a business plan; tag Past due so Billing can filter it on the kanban.

Permission: Manage conversations.

Send at least one of the three. They can be sent together: the API starts from etiquetas (or from the current tags, without it), adds adicionar and removes remover. Lists accept JSON ([1, 3]), form fields (adicionar[]=1&adicionar[]=3) or comma separated text (adicionar=1,3). Repeated ids are ignored.

# adds tags 1 and 3 and removes tag 2
curl -s -X POST "https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/etiquetas" \
  -H "Authorization: Bearer $CHATISP_CHAVE" \
  -H "Content-Type: application/json" \
  -d '{"conversa_id": 18342, "adicionar": [1, 3], "remover": [2]}'

# clears them all
curl -s -X POST "https://atendimento.seuprovedor.com.br/api_publica.php" \
  -H "Authorization: Bearer $CHATISP_CHAVE" \
  -d "r=conversas/etiquetas" -d "conversa_id=18342" -d "etiquetas="

<?php
$ch = curl_init('https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/etiquetas');
curl_setopt_array($ch, [
    CURLOPT_POST           => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => ['Authorization: Bearer ' . getenv('CHATISP_CHAVE'), 'Content-Type: application/json'],
    CURLOPT_POSTFIELDS     => json_encode(['protocolo' => '20261001-0042', 'etiquetas' => [1]]),
]);
$r = json_decode(curl_exec($ch), true);
curl_close($ch);
echo implode(', ', array_column($r['conversa']['etiquetas'], 'nome')), PHP_EOL;

import os, requests

r = requests.post("https://atendimento.seuprovedor.com.br/api_publica.php",
    params={"r": "conversas/etiquetas"},
    headers={"Authorization": "Bearer " + os.environ["CHATISP_CHAVE"]},
    json={"conversa_id": 18342, "adicionar": [3]}, timeout=30)
print([e["nome"] for e in r.json()["conversa"]["etiquetas"]])

{
  "ok": true,
  "conversa": {
    "id": 18342,
    "protocolo": "20261001-0042",
    "...": "other fields of the conversation object",
    "etiquetas": [
      { "id": 1, "nome": "VIP", "cor": "#f59e0b" },
      { "id": 3, "nome": "Technician visit", "cor": "#2563eb" }
    ]
  }
}

{"ok": false, "error": "etiqueta_invalida", "campo": "adicionar"}

Route-specific errors: parametro_obrigatorio (none of the three; campo set to etiquetas|adicionar|remover), etiqueta_invalida (id not found; nothing is changed), parametro_invalido, identificador_obrigatorio, nao_encontrado.

Writes a note in the conversation timeline, visible to the team only. Examples: the NOC reports a fiber cut in the customer's area; the ERP records that the payment cleared during the service.

Permission: Manage conversations.

• The note appears in the chat as a system line, with the key name in front: API (ERP): Payment cleared at 10:12 AM.
• It is never sent to the customer, is not part of the history the AI reads and does not appear in reports.
• It also does not come back through the API read routes (which never return internal content): store the nota_id if you need to reference it.

curl -s -X POST "https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/nota" \
  -H "Authorization: Bearer $CHATISP_CHAVE" \
  -H "Content-Type: application/json" \
  -d '{"protocolo": "20261001-0042", "texto": "Fiber cut in the Jardim Alvorada neighborhood, expected fix at 2 PM."}'

<?php
$ch = curl_init('https://atendimento.seuprovedor.com.br/api_publica.php?r=conversas/nota');
curl_setopt_array($ch, [
    CURLOPT_POST           => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => ['Authorization: Bearer ' . getenv('CHATISP_CHAVE'), 'Content-Type: application/json'],
    CURLOPT_POSTFIELDS     => json_encode(['conversa_id' => 18342, 'texto' => 'Payment cleared at 10:12 AM.']),
]);
$r = json_decode(curl_exec($ch), true);
curl_close($ch);

import os, requests

r = requests.post("https://atendimento.seuprovedor.com.br/api_publica.php",
    params={"r": "conversas/nota"},
    headers={"Authorization": "Bearer " + os.environ["CHATISP_CHAVE"]},
    json={"conversa_id": 18342, "texto": "Payment cleared at 10:12 AM."}, timeout=30)
print(r.json())

{"ok": true, "nota_id": 402990, "conversa_id": 18342}

Route-specific errors: texto_invalido (empty or over 900 characters), identificador_obrigatorio, nao_encontrado.

Puts a phone number in the service queue (or straight with an agent) without sending any message to the customer. This is the way to go when the request starts outside WhatsApp: website contact form, subscriber portal, monitoring system alarm, scheduled callback. The team sees the service request in the panel and talks to the customer from there.

Permission: Open service requests.

How the call behaves

1. ChatISP looks for an open conversation of this phone number on the WhatsApp number (across both channels of a twin number, with and without the ninth digit). If there is none, it creates a new one, in the queue, with its own protocol number (the conversa_criada webhook fires).
2. The nota, if sent, is written to the timeline, along with the key record.
3. With atendente_id: the conversation goes straight to that agent (state humano), whatever state it was in, and also to the departamento_id, if sent. It leaves the AI or the flow, if it was in them. The agent is notified.
4. Without atendente_id, with the conversation in the queue: it goes to the queue of the requested departamento_id (or stays in the current department queue), and automatic distribution tries to deliver it right away. If an agent is available, it already comes out as humano; otherwise it stays fila and the team gets the alert.
5. Without atendente_id, with the conversation with the AI, in a flow or already with an agent: nothing changes, not even the department. The API does not pull a conversation that is already being handled.

curl -s -X POST "https://atendimento.seuprovedor.com.br/api_publica.php?r=atendimentos/abrir" \
  -H "Authorization: Bearer $CHATISP_CHAVE" \
  -H "Content-Type: application/json" \
  -d '{
    "telefone": "5544988887777",
    "nome": "João Pereira",
    "departamento_id": 2,
    "nota": "Asked through the portal to renegotiate the September invoice."
  }'

<?php
$ch = curl_init('https://atendimento.seuprovedor.com.br/api_publica.php');
curl_setopt_array($ch, [
    CURLOPT_POST           => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => ['Authorization: Bearer ' . getenv('CHATISP_CHAVE')],
    CURLOPT_POSTFIELDS     => http_build_query([
        'r'               => 'atendimentos/abrir',
        'telefone'        => '5544988887777',
        'nome'            => 'João Pereira',
        'departamento_id' => 2,
        'nota'            => 'Asked through the portal to renegotiate the September invoice.',
    ]),
]);
$r = json_decode(curl_exec($ch), true);
curl_close($ch);
echo $r['ja_existia'] ? 'A service request already existed: ' : 'Service request opened: ', $r['protocolo'], PHP_EOL;

import os, requests

r = requests.post("https://atendimento.seuprovedor.com.br/api_publica.php",
    params={"r": "atendimentos/abrir"},
    headers={"Authorization": "Bearer " + os.environ["CHATISP_CHAVE"]},
    json={
        "telefone": "5544988887777",
        "atendente_id": 7,
        "nota": "Callback scheduled by the NOC.",
    }, timeout=30)
corpo = r.json()
print(corpo["protocolo"], corpo["estado"], corpo["ja_existia"])

{
  "ok": true,
  "conversa_id": 18361,
  "protocolo": "20261001-0056",
  "estado": "fila",
  "ja_existia": false,
  "conversa": {
    "id": 18361,
    "protocolo": "20261001-0056",
    "conexao_id": 1,
    "telefone": "5544988887777",
    "nome": "João Pereira",
    "estado": "fila",
    "departamento_id": 2,
    "departamento": "Billing",
    "...": "other fields of the conversation object",
    "etiquetas": []
  }
}

Route-specific errors: telefone_invalido, conexao_invalida, sem_conexao, conexao_id_obrigatorio, conexao_desconectada, departamento_invalido, atendente_invalido, texto_invalido (note over 900 characters, with campo set to nota).