X / Twitter Транскрипт твита API
Извлекает произнесённый транскрипт из твита Twitter/X с видео по URL.
1,20 USD/1 тыс. запросов, оплата за запрос, без подписки.
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."}
Цены и поставщики
Цена API X / Twitter Транскрипт твита: один API, поставщиков 2, и любой может заменить другого
Первым обслуживает самый дешёвый поставщик. Если он не отвечает, его заменяет следующий в том же вызове.
Вызвать
Получите X / Twitter Транскрипт твита одним запросом
import os, requests res = requests.post( "https://api.getanyapi.com/v1/run/twitter.tweet_transcript", headers={"Authorization": f"Bearer {os.environ['ANYAPI_KEY']}"}, json={ "url": "" }, ) print(res.json())
{
"found": true,
"data": {
"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."
}
}Полный справочник по параметрам и ответу: каждое поле, тип и пример для этого эндпоинта.
Справочник
Один запрос, один формат ответа.
Каждое поле, которое вы отправляете, и каждое поле, которое получаете, с реальным примером.
Проверено 2026-10-07 · доступность и задержка измерены за 30d
Тело запроса
JSON, отправляется на этот эндпоинт.
- urlstring
https://x.com/buildwithjonah/status/1842093771280384512
URL твита с видео для расшифровки (например, https://x.com/TheoVon/status/1916982720317821050).
Ответ
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.
Вопросы и ответы
Об API X / Twitter Транскрипт твита
AnyAPI X / Twitter Транскрипт твита API возвращает данные X / Twitter в виде нормализованного JSON одним вызовом POST к /v1/run/twitter.tweet_transcript. Извлекает произнесённый транскрипт из твита Twitter/X с видео по URL. AnyAPI направляет каждый запрос по источникам (их 2) и автоматически переключается, если один из них отказывает. Это стоит от 1,20 USD за 1000 запросов, в долларах США, без подписки и без ежемесячного минимума. За последние 30 дней 100,0% вызовов X / Twitter Транскрипт твита через AnyAPI завершились успешно, медианное время ответа 3,6 с, измерено вызовов: 20.