Trump Truth Pulse measures, it does not advise. This is not financial advice: you place the orders with your own broker and the risk stays yours.
Trump Truth Pulse
API v1

API documentation

All requests are GET and require a key in the Authorization header. Responses are UTF-8 JSON. The version is part of the path: within v1 we never remove or rename fields, we only add them.

Start here

Three commands and you have your first event. Create the key in your account area.

# 1. la chiave funziona? e da dove ripartire?
curl -H "Authorization: Bearer $KEY" https://trumptruthpulse.it/api/v1/stato

# 2. il primo blocco di eventi (dall'inizio dello storico)
curl -H "Authorization: Bearer $KEY" "https://trumptruthpulse.it/api/v1/eventi?dopo=0&limite=50"

# 3. da qui in avanti: rimanda il cursore che hai ricevuto
curl -H "Authorization: Bearer $KEY" "https://trumptruthpulse.it/api/v1/eventi?dopo=<prossimo_cursore>"

To start from NOW instead of from history, read cursore_attuale from /stato and use it as your first "dopo". In production prefer the webhook anyway: we call you, and polling stays the safety net.

Authentication

Keys are created in your account area and shown only once. If you lose one, revoke it and create another: we cannot show it again because we only keep its fingerprint.

curl -H "Authorization: Bearer ttp_live_..." \
  https://trumptruthpulse.it/api/v1/stato

Two errors worth telling apart: 401 means the key is missing, wrong or revoked; 402 means the key is valid but the subscription is not active. The first is fixed in code, the second in billing.

{"errore":{"codice":"abbonamento_non_attivo","messaggio":"...","message":"..."}}
Endpoints
GET /api/v1/eventi?dopo=<cursore>&limite=<1..500>
GET /api/v1/eventi/<evento_id>
GET /api/v1/post/<id>
GET /api/v1/stato

Events come in ascending chronological order. Keep "prossimo_cursore" and send it back as "dopo": repeat until "altri" is false. The cursor is monotonic, so you lose nothing even after hours offline.

curl -H "Authorization: Bearer $KEY" \
  "https://trumptruthpulse.it/api/v1/eventi?dopo=0&limite=100"

{
  "eventi": [ ... ],
  "prossimo_cursore": "1842",
  "altri": false,
  "sorgente_ok": true,
  "ultimo_controllo": "2026-07-23T12:37:02+00:00"
}

To start from now without downloading history, read "cursore_attuale" from /api/v1/stato and use it as your first "dopo". The same endpoint tells you whether the detector is running: sorgente_ok false means the source is temporarily down, so no new events are coming in.

Event format
tipowhenwhat it carries
post.rilevatoas soon as we see the postmisure: absent · segnale: null
misure.ampiezzaonce the reaction is setmisure: 17 · segnale: present (action and markets)
misure.chiusewhen measurements are donemisure: 17 · segnale: present · esito: if a trade was opened

Three events per RELEVANT post, not one per market: post.rilevato as soon as the post is seen, misure.ampiezza once the first reaction is set across the 17 markets, misure.chiuse when measurements are done. Posts the filter discards produce no events at all: we see and measure them for context, but we do not send them to you. On post.rilevato the misure field is null: there is nothing to read yet.

{
  "evento_id": "evt_1842_ampiezza",
  "tipo": "misure.ampiezza",
  "creato": "2026-07-23T12:32:10+00:00",
  "post": {
    "id": 1842,
    "sorgente_id": "3ktz...",
    "autore": "trump",
    "url": "https://...",
    "pubblicato": "2026-07-23T12:29:00+00:00",
    "rilevato": "2026-07-23T12:32:08+00:00",
    "testo_en": "...",
    "testo_it": "...",
    "rilevante": true
  },
  "misure": [
    { "asset": "XAG", "etichetta": "Argento", "prezzo_t0": 58.91,
      "ampiezza_pct": 0.42, "variazione_pct": -0.42, "insolito": 3.4,
      "rientro_min": 18, "stato": "completa", "nota": null }
  ],
  "segnale": {
    "azione": "vendi", "verso": "giu",
    "misurati": 17, "concordi": 11, "insolito_medio": 3.2,
    "concordi_asset": ["BTC", "XAG", "WTI", "QQQ", "SPY"],
    "contro_asset": ["XAU"],
    "avvertenza": "..."
  },
  "concorrenza": { "quanti": 1, "voci": { "fed": 1 } },
  "esito": null
}

About dates. They are all ISO-8601 in UTC (+00:00). pubblicato is the time declared by the source we take the post from: when the same post reaches us from both sources we keep the older of the two, if they are at least half a minute apart; when only one arrives its time is what we have, and it can be a few minutes later. rilevato is when we saw it, and the gap between the two is not our latency.

Two fields worth watching. concorrenza counts the OTHER POSTS published inside the measurement window (from one minute before the post to five minutes after): `quanti` is the total, `voci` groups them by author. Above zero the move is contested and the cause is not that post alone - we say it first, because otherwise we would be selling you a causation we have not shown. It also counts other posts by the same author and posts the filter discarded: it is context, not a verdict. esito appears only on misure.chiuse and carries the closed trade: average theoretical return, the same the other way round, the minute the last market exited, and the per-market breakdown. It is null on the other two events and on any post that came out neutral, because no trade was ever opened.

// dentro misure.chiuse
"esito": {
  "azione": "compra", "chiusa": true,
  "rendimento": -0.089, "rendimento_contrario": 0.089,
  "minuto_uscita": 6,
  "mercati": [ { "asset": "DIA", "nome": "Dow Jones",
                 "nome_en": "Dow Jones", "rendimento": 0.062 } ],
  "avvertenza": "...", "avvertenza_en": "..."
}

ampiezza_pct is the largest percentage swing in the 5 minutes after the post. rientro_min is the first minute when price gives back more than half of that swing: null if it has not happened yet, or did not happen within two hours (state "timeout"). The 17 markets: BTC, EUR/USD, Gold, Silver, S&P 500, Nasdaq, Dow Jones, Oil, Nat gas, Copper, Yuan, Peso, Treasuries, Volatility, Italy, Germany, Euro Stoxx. Gold, silver and oil are the real instrument; the three US stock indices are measured through ETFs, because the official indices require a licence: we say so because the number should be interpretable, it is not a hidden detail.

The signal block (absent on post.rilevato, present on measurement events) summarises the markets: azione is "vendi" (sell), "compra" (buy) or "neutro"; concordi_asset is what the action refers to, strongest first, and when there is an action it holds only the markets that clear the movement threshold on their own, the ones worth trading; concordi_tutti lists every market moving the prevailing way, including the nearly still ones; sopra_soglia gives the action markets with their amplitude; contro_asset lists those moving the other way. Some markets are INVERSE by construction (yuan, Mexican peso, Treasuries and volatility rise when equities fall): they count towards agreement with their sign flipped, so a rise in them confirms a "vendi", but they never appear in concordi_asset, because the object of the action must be executable exactly as written. It is an automated computation on market data, not an investment recommendation: the disclaimer travels inside the payload.

Webhooks and signature

Register an https address in your account area and we POST every event to it, before the notification goes out on the human channels. You must answer 2xx within 3 seconds. If you do not, we retry after 1 minute, 5, 15, an hour and 6 hours: meanwhile events stay readable by polling, so nothing is lost.

POST /il-tuo-endpoint
Content-Type: application/json
X-TTP-Evento: evt_1842_rilevato
X-TTP-Tentativo: 1
X-TTP-Signature: t=1753280000,v1=<hmac_sha256("{t}.{corpo}", secret)>

Always verify the signature before trusting the body, and reject messages whose t is older than 5 minutes. Compare in constant time.

# Python
import hmac, hashlib, time
t, v1 = dict(p.split('=', 1) for p in firma.split(',')).values()
atteso = hmac.new(secret.encode(), f"{t}.{corpo}".encode(), hashlib.sha256).hexdigest()
assert hmac.compare_digest(atteso, v1) and abs(time.time() - int(t)) <= 300

The same event may arrive more than once (a retry after a lost response, for instance). evento_id is stable: use it to drop duplicates. We do not follow redirects: the address you register is the one we call.

Limits and plans

Every authenticated response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (401 and 402 responses do not: the key is not known yet). Over the limit we answer 429 with Retry-After: wait that long instead of hammering. Limits are per key, so more keys multiply the ceiling.

Paid plan   600 req/min per key     no monthly quota       real time, 3 webhooks  full history
Timing, guarantees and permitted use

An event is born when our detector sees the post, and is sent right after. How long it takes between publication and the event is decided by the source, not by us: we watch more than one in parallel and whichever gets there first wins. In our sequence the webhook goes out BEFORE the human channels: the event leaves, then the post is translated, and only then Telegram and ntfy fire. The head start is a few seconds and is not guaranteed: that is not what you buy the API for, you buy it because the event reaches a program instead of a person. There is no latency SLA and we do not promise source continuity: if it goes down, sorgente_ok turns false and already detected events stay readable. Internal-use plans do not include the right to redistribute events to your own end users: that needs a dedicated agreement.

See the plansTerms of use

We only use technical cookies, the ones that make the site work: they keep you logged in, protect the forms and remember your language. No profiling, no advertising trackers, nothing to accept. Details