X / Twitter Transcription du tweet API
Extrait la transcription parlée d’un tweet vidéo Twitter/X à partir de son URL.
1,20 $US/1k req, paiement à la requête, sans abonnement.
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."}
Tarifs et fournisseurs
Tarifs de l’API X / Twitter Transcription du tweet : une API, 2 fournisseurs interchangeables
Le fournisseur le moins cher répond en premier. S’il échoue, le suivant prend le relais dans le même appel.
L’appeler
Obtenez X / Twitter Transcription du tweet en une requête
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."
}
}Référence complète des paramètres et de la réponse : chaque champ, type et exemple de cet endpoint.
Référence
Une requête, une seule forme de réponse.
Chaque champ que vous envoyez et chaque champ que vous recevez, avec un vrai exemple.
Dernière vérification : 2026-10-07 · disponibilité et latence mesurées sur 30d
Corps de la requête
JSON, envoyé à cet endpoint.
- urlstring
https://x.com/buildwithjonah/status/1842093771280384512
URL du tweet de la vidéo à transcrire (p. ex. https://x.com/TheoVon/status/1916982720317821050).
Réponse
JSON, une valeur d’exemple par champ.
- 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.
FAQ
À propos de l’API X / Twitter Transcription du tweet
L’API X / Twitter Transcription du tweet d’AnyAPI renvoie des données X / Twitter en JSON normalisé à partir d’un appel POST à /v1/run/twitter.tweet_transcript. Extrait la transcription parlée d’un tweet vidéo Twitter/X à partir de son URL. AnyAPI route chaque requête sur 2 sources et bascule automatiquement quand l’une échoue. Elle coûte à partir de 1,20 $US pour 1 000 requêtes, en dollars US, sans abonnement et sans minimum mensuel. Ces 30 derniers jours, 100,0% des appels X / Twitter Transcription du tweet passés par AnyAPI ont réussi, avec un temps de réponse médian de 3,6 secondes, sur 20 appels mesurés.