Trump Truth Pulse API
The same events we push to Telegram and ntfy, machine-readable: the post as soon as it is detected, the measured reaction across 17 markets and, when the numbers are clear-cut, the action with the names of the markets behind it. Push delivery via signed webhook or read by polling.
{
"evento_id": "evt_1842_ampiezza",
"tipo": "misure.ampiezza",
"creato": "2026-07-23T12:32:10+00:00",
"post": {
"id": 1842,
"autore": "trump",
"url": "https://...",
"pubblicato": "2026-07-23T12:29:00+00:00",
"testo_en": "...",
"testo_it": "..."
},
"misure": [
{ "asset": "XAG", "etichetta": "Argento", "ampiezza_pct": 0.47,
"variazione_pct": -0.47, "rientro_min": 16, "stato": "completa" },
{ "asset": "QQQ", "etichetta": "Nasdaq (QQQ)", "ampiezza_pct": 0.30,
"variazione_pct": -0.30, "rientro_min": 5, "stato": "completa" },
{ "asset": "BTC", "etichetta": "BTC", "ampiezza_pct": 0.27,
"variazione_pct": -0.27, "rientro_min": 12, "stato": "completa" }
],
"segnale": {
"azione": "vendi",
"concordi_asset": ["XAG", "QQQ", "BTC"],
"misurati": 17, "concordi": 11, "insolito_medio": 3.2,
"avvertenza": "Segnale automatico da dati di mercato, non e consulenza..."
}
}
Shortened example: the real payload carries seventeen measurements, one per market. On post.rilevato the signal block is null, and the three markets listed here are exactly the ones that clear the movement threshold on their own: they are the object of the action.
Everything there is, no tiers: real-time events, 3 signed webhook endpoints, 5 keys, 600 requests per minute and the full history. One plan, no choice to make and nothing to unlock later.
Launch price, and it will go up. The first 100 API customers keep this price for life, even after the increases. We count the seats: when they run out, the offer closes.
Get the APIShowing events to your own end users requires a dedicated agreement. Pricing depends on how many people see the data, not on traffic: it starts at 490 €/month up to one thousand end users and scales in tiers. Volumes, endpoints, attribution and terms are agreed by contract.
Contact usHonest about timing: the event is born when our detector sees the post, and goes out right after. We publish no delivery times and give no latency SLA, because the gap between the post and the event is decided by the source, not by us: we watch several sources in parallel and whichever gets there first wins. On our side, though, the event goes out to the API BEFORE the message is translated and pushed to Telegram: a few seconds of head start, not an order of magnitude. The real advantage is different: the event reaches a program, which acts in milliseconds, while a notification has to be read by a person.