Post
buildwithjonah
@buildwithjonah
Transcript
Alright so I spent the last six months building a data pipeline that normalizes about forty different scraper APIs into one schema. I want to walk through what broke and what I would do differently if I started over today. The first lesson was that every provider's error format is completely different. Some return a 200 with an error field buried three levels deep, some return a real HTTP error code, and some just silently return an empty array. We ended up writing a translation layer just so our retry logic actually knew whether a failure meant retry later or never retry at all. The second lesson was around pagination. Cursors are never portable across providers, so we had to build our own cursor abstraction just to keep the client code simple and predictable.
{"transcript": "Alright so I spent the last six months building a data pipeline that normalizes about forty different scraper APIs into one schema. I want to walk through what broke and what I would do differently if I started over today. The first lesson was that every provider's error format is completely different. Some return a 200 with an error field buried three levels deep, some return a real HTTP error code, and some just silently return an empty array. We ended up writing a translation layer just so our retry logic actually knew whether a failure meant retry later or never retry at all. The second lesson was around pagination. Cursors are never portable across providers, so we had to build our own cursor abstraction just to keep the client code simple and predictable."}
价格与服务商
X / Twitter 推文转录文本 API 价格：一个 API，2 个可互换的服务商
最便宜的服务商优先响应。如果它失败，下一个会在同一次调用中接手。
参考
一个请求，一种响应结构。
你发送的每个字段和收到的每个字段，都附有真实示例。
最近验证于 2026-10-06 · 可用率和延迟按 30d 统计
请求体
JSON，POST 到这个接口。
- urlstring
https://x.com/buildwithjonah/status/1842093771280384512
响应
JSON，每个字段一个示例值。
- foundboolean
true
- transcriptstring
Alright so I spent the last six months building a data pipeline that normalizes about forty different scraper APIs into one schema. I want to walk through what broke and what I would do differently if I started over today. The first lesson was that every provider's error format is completely different. Some return a 200 with an error field buried three levels deep, some return a real HTTP error code, and some just silently return an empty array. We ended up writing a translation layer just so our retry logic actually knew whether a failure meant retry later or never retry at all. The second lesson was around pagination. Cursors are never portable across providers, so we had to build our own cursor abstraction just to keep the client code simple and predictable.
常见问题
关于 X / Twitter 推文转录文本 API
AnyAPI 的 X / Twitter 推文转录文本 API 只需一次 POST 请求 /v1/run/twitter.tweet_transcript，就以统一格式的 JSON 返回 X / Twitter 数据。通过 URL 从 Twitter/X 视频推文中提取语音转录文本。AnyAPI 会在 2 个数据源之间路由每个请求，某个数据源失败时自动切换。费用：每千次请求 US$1.20 起，以美元计价，无需订阅，也没有每月最低消费。过去 30 天，通过 AnyAPI 发起的 X / Twitter 推文转录文本 API 调用中有 100.0% 成功，响应时间中位数为 3.6 秒，共测量 20 次调用。