Telegram rich messages

​

Send formatted content

curl -X POST https://api.dairo.app/v1/messages \
  -H "Authorization: Bearer $DAIRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "inboxId": "inbox_9f2b...",
    "to": ["telegram:5031234567"],
    "html": "<b>Deploy finished</b>\n<i>3 services</i>, <s>0</s> errors.\nDetails: <a href=\"https://status.acme.dev\">status page</a>"
  }'

await dairo.messages.send({
  inboxId: "inbox_9f2b...",
  to: ["telegram:5031234567"],
  html: [
    "<b>Deploy finished</b>",
    "<i>3 services</i>, <s>0</s> errors.",
    'Details: <a href="https://status.acme.dev">status page</a>',
  ].join("\n"),
});

​

What you can format

​

A status report

<h3>Nightly run — Q1 pipeline</h3>
<ul>
  <li><b>Ingested</b> 1.2M rows</li>
  <li><b>Failed</b> <tg-spoiler>3</tg-spoiler> (retrying)</li>
</ul>
<blockquote>Next run at 02:00 UTC.</blockquote>

​

A table of results

<table>
  <tr><th>Metric</th><th>Value</th></tr>
  <tr><td>Latency p50</td><td><b>42 ms</b></td></tr>
  <tr><td>Errors</td><td>0</td></tr>
</table>

​

An inline image

<img src="https://cdn.acme.dev/signups.png"/>
<b>Signups this week</b>

​

Patterns for agents

• Lead with a heading. A <h3> title makes a status update scannable in the chat list.
• Tables for numbers, lists for steps. Reserve prose for the one line that matters.
• Spoilers for noise. Wrap long stack traces or optional detail in <tg-spoiler> so the summary stays clean.
• Split long reports. A very long report reads better as a few sends — one heading per send keeps each scannable in the chat list.
• Always have a plain fallback. When you don’t need formatting, send text — it’s faster to compose and impossible to mis-escape.

​

Next steps