CovfefeTruth Social API and webhooks for traders (without the official API)
Search for a Truth Social API and you will find unofficial docs, scraper repos, n8n templates, Discord bots, and commercial pipes aimed at millisecond buyers. What most traders and automation builders actually want is simpler: when @realDonaldTrump posts on Truth Social, hit my endpoint (or notify me) within seconds—reliably—and optionally indicate whether the post looks market-relevant.
That is not the same as being Truth Social’s official API. Covfefe is not that. This article covers how a signed webhook workflow works for Trump Truth Social posts, how Covfefe structures events, how that compares to DIY and millisecond feeds, and when Telegram is a better interface than JSON. Covfefe is not affiliated with Truth Social, TMTG, or Donald Trump.
What people mean by “Truth Social API”
In practice, the phrase covers four jobs:
- Read Trump’s latest posts programmatically (the dominant use case for traders and newsrooms).
- Build apps on Truth Social’s platform (official developer surface—if it fits).
- Scrape or poll public HTML or JSON (fragile, yours to maintain).
- Buy a latency product aimed at HFT-style detection (different buyer and budget).
If you are a discretionary trader, a systematic desk that is not co-located for this feed, a newsletter, or a newsroom bot, you are almost always in bucket 1—with a preference for webhooks over polling your own scraper.
The Covfefe model: alerts first, enrichment second
Covfefe watches new @realDonaldTrump Truth Social posts and delivers them via Telegram or a signed webhook. Most posts arrive within seconds of going public on Truth Social. Late catch-up after an outage is marked delayed.
Enrichment lands about 2 seconds later: Covfefe's automated relevance score (0–10), topics, tickers/entities, and a plain-English summary. That is context for triage, not a market forecast. Positioning: a feed for people who do not need a $100k/month data budget. Firms racing in milliseconds should buy official or priority feeds instead.
Pricing: Telegram DMs at $29/mo; signed webhooks at $99/mo.
Event types: post.created vs post.enriched
| Event | When it fires | What it is for |
|---|---|---|
post.created |
As soon as Covfefe detects the new post | Wake your bot, notify, log raw content |
post.enriched |
~2 seconds later | Triage with score, topics, entities, summary |
Why split them? You should not wait on enrichment to learn that a post exists. Raw detection first; scoring as a second pass.
detected_at, signing, retries, delivery log
Webhook payloads carry detected_at: when Covfefe saw the post. Use it to measure end-to-end latency, distinguish fresh events from delayed replay, and debug missed deliveries.
Signed means you can verify the request came from Covfefe—not a random POST. Treat verification as mandatory in production. Retries mean transient 500s on your side do not equal permanent data loss. A delivery log means you can answer whether Covfefe sent post.created for a given post.
None of this makes Covfefe an official Truth Social API. It makes it a productized alert pipe with reliability features traders and newsrooms need.
Telegram for humans, webhooks for bots
- Telegram: practical for discretionary traders, editors, and anyone who should look at a phone when a post appears.
- Webhooks: better for bots, Slack bridges, research logs, dashboards, and threshold-based automation.
Same underlying detection. Different last mile. Many teams run both.
Honest comparison: DIY vs Covfefe vs millisecond feeds
DIY scrape / n8n / homegrown poller
Good when: you enjoy maintenance and downtime is annoying rather than expensive.
Pain when: selectors change, rate limits bite, or the one post that mattered arrived while your scraper was down.
Covfefe (human-speed + enrichment)
Good when: you need seconds, signed delivery, Telegram and/or webhooks, and optional enrichment—without staffing a scraper.
Not for: claiming microsecond advantage or replacing a priority feed in an HFT stack.
Latency: usually within seconds of a post going public, delayed flag when catch-up is late. Enrichment ~2 seconds after create.
Millisecond / priority feeds (e.g. tools like 1322.io)
Good when: your strategy’s edge is the race itself. Check their sites for current terms; we do not invent competitor prices or SLAs.
Wrong when: you are a person who would still be reading the post 20 seconds later.
If you are racing in milliseconds, buy the feed built for that.
A minimal webhook workflow
- Expose an HTTPS endpoint that verifies Covfefe’s signature.
- On
post.created, store the post, notify if needed, start work that does not need scores. - On
post.enriched, attach Covfefe's automated relevance score, topics, entities, and summary; branch on thresholds you define. - Use
detected_atfor latency metrics and for interpreting delayed deliveries. - Keep a human Telegram channel as a fail-safe.
What enrichment is—and is not
Enrichment is a second event, not a substitute for reading.
- Score 0–10 = triage hint via Covfefe's automated relevance score.
- Topics / tickers / entities = structured handles for filters and logs.
- Plain-English summary = faster scanning under pressure.
It is not a buy/sell signal, and it is not a promise that the model never misses sarcasm or fast-moving entity names. Treat it as context.
Soft CTA
If you searched for a Truth Social API because you need Trump posts in your stack, try Covfefe’s signed webhooks (and Telegram) at covfefe.app. post.created, then post.enriched. Seconds for humans and sane bots. Millisecond races should shop elsewhere.
FAQ
Is Covfefe the official Truth Social API?
No. It delivers alerts and enrichment for @realDonaldTrump posts via Telegram or signed webhooks. It is not affiliated with Truth Social, TMTG, or Donald Trump.
What is in post.created vs post.enriched?
post.created is detection. post.enriched follows ~2 seconds later with Covfefe's automated relevance score, topics, tickers/entities, and a plain-English summary.
How fast is webhook delivery?
Usually within seconds of the post going public. Late alerts after outages are marked delayed.
Should traders use Telegram or webhooks?
People: Telegram. Bots and pipelines: webhooks. Many use both. Telegram DMs are $29/mo; signed webhooks are $99/mo.
How is this different from an n8n DIY template?
Templates shift maintenance to you. Covfefe productizes detection, signing, retries, delivery logs, and enrichment.
Covfefe publishes information, not investment advice. Nothing here is a recommendation to buy, sell, or hold any asset. Quoted posts link to their original source.