开发者参考
将 Truth Social 警报集成到交易机器人、控制台和自动化管道中。Webhook和 REST 访问需要商业版或以上计划。
Programmatic access works differently from Telegram and email alerts: instead of reading a notification, your own application processes the events. Here's how to set it up.
Telegram and email alerts remain available on every plan independent of this — this section covers programmatic access (webhook/REST) only.
TruthPush 通过两种集成路径提供丰富的帖子事件（情绪、带符号的得分、交易代码和关键词）：
Telegram 和电子邮件警报使用单独的频道；本参考仅涵盖程序化访问。
REST 请求使用 Bearer 令牌。相同的密钥会对Webhook负载进行签名。
curl "https://truthpush.com/api/v1/posts/catch-up?handle=realDonaldTrump&limit=20" \
-H "Authorization: Bearer YOUR_API_TOKEN"请像对待密码一样对待您的 API 令牌。重新生成会立即使之前的令牌和Webhook签名失效。
在 TruthTerminal 中配置您的Webhook URL。每个符合条件的帖子都会触发一个带有 JSON 正文和 TruthPush 签名标头的 HTTP POST 请求。
POST https://your-server.com/hooks/truthpush
Content-Type: application/json
X-TruthPush-Signature: t=<unix>,v1=<hmac_sha256_hex>
X-TruthPush-Event-Id: <post_id>
v1 = HMAC_SHA256(api_token, "<t>." + raw_body)Reference implementation for receivers — checks the replay window and compares the signature in constant time.
import hmac
import hashlib
import time
TOLERANCE_SECONDS = 300 # reject requests older than 5 minutes
def verify_signature(payload: bytes, secret: str, header: str) -> bool:
parts = dict(p.split("=", 1) for p in header.split(","))
timestamp, signature = int(parts["t"]), parts["v1"]
if abs(time.time() - timestamp) > TOLERANCE_SECONDS:
return False # possible replay attack
signed_payload = f"{timestamp}.".encode() + payload
expected = hmac.new(secret.encode(), signed_payload, hashlib.sha256).hexdigest()
return hmac.compare_digest(expected, signature)
# Flask example
# signature_header = request.headers["X-TruthPush-Signature"]
# if not verify_signature(request.get_data(), API_TOKEN, signature_header):
# abort(401)在 TruthTerminal 中设置最低绝对 signed_score（0 = 所有事件，0.7 = 仅强信号）以减少交易管道中的噪音。
每个符合条件的帖子只会触发一次 Webhook 投递——包含原始帖子内容和分析完成后的情绪判断，会在 AI 情绪分析完成后立即发送（通常在几秒钟内）。投递使用独立队列并自动重试，绝不会因为向其他用户发送 Telegram 或邮件通知而延迟。
GET /api/v1/posts/catch-up
使用游标分页按时间升序返回句柄的帖子。响应会被短暂缓存（约7秒），并支持 ETag / If-None-Match 以实现高效轮询。
Start with the first request without a cursor. Every response includes meta.next_cursor — pass it unchanged into the next request until it is null.
# 1) First request — no cursor yet
curl "https://truthpush.com/api/v1/posts/catch-up?handle=realDonaldTrump&limit=100" \
-H "Authorization: Bearer YOUR_API_TOKEN"
# Response (truncated):
# { "posts": [ … 100 items … ],
# "meta": { "next_cursor": "eyJpZCI6MTIzNDU2fQ==" } }# 2) Follow-up request — pass the cursor from meta.next_cursor
curl "https://truthpush.com/api/v1/posts/catch-up?handle=realDonaldTrump&cursor=eyJpZCI6MTIzNDU2fQ%3D%3D&limit=100" \
-H "Authorization: Bearer YOUR_API_TOKEN"
# meta.next_cursor is null once you've reached the latest postWebhook负载和 REST 帖子对象共享相同的丰富字段。event_id 等于 post_id，供您在系统端去重。
{
"event_id": "1234567890",
"target": "realdonaldtrump",
"post_id": "1234567890",
"content": "Post text…",
"url": "https://truthsocial.com/@realdonaldtrump/posts/1234567890",
"media": [],
"sentiment": "bullish",
"signed_score": 0.89,
"score": 0.89,
"tickers": ["$DJT"],
"keywords": ["tariffs", "trade"],
"reasoning": "Direct market impact via trade policy.",
"ai_analysis": { … }
}限制适用于每个 API 令牌。超出限制将返回 HTTP 429 和 Retry-After。
观察者或专业版不提供 API 和Webhook功能。TruthTerminal 实时动态从专业版开始提供；程序化访问从商业版开始。
常见 API 响应：
正在重定向至我们的支付服务商