X (Twitter) data API.
Get profiles, posts, and Communities through one documented REST API.
- 100 free API credits included
- No payment card required
- Failed requests cost 0 credits
X (Twitter) API endpoints.
Get profiles, recent posts, single posts, and Communities. Every call costs 1 credit.
X (Twitter) live demo.
Run a live request. No account or API key needed.
Current public data
Use Run to fetch a live response from the Tapline API.
Start free.
Scale when you need to.
Use one credit pool across every live Tapline API. Upgrade only when you need more requests or a higher rate limit.
Pay As You Go
Starter
Enterprise
X (Twitter) API questions.
Sign up to get 100 free API credits with no card required, then create an API key in the dashboard. Send it in the X-API-Key header and you can make your first request in under a minute.
No. Tapline returns publicly available X data. Fields that are not publicly available, such as listed_count or a post source, are omitted rather than filled with placeholders.
User posts returns the pinned post and newest original posts, usually 5 in all. Community posts returns the 20 most-liked posts. Neither endpoint has a cursor.
Yes. Pass the numeric user_id to the profile endpoint instead of handle. Send one or the other, not both.
Calls fetch the page at request time. Profile pages are cached for 2 minutes, so a profile and its posts can be up to 2 minutes old.
Yes. Your plan has one credit pool shared across every live Tapline API.
Credits are charged when Tapline reaches the target and receives a valid response about the requested resource. This includes responses showing that the resource is private, restricted, unavailable, or does not exist. Requests that fail because Tapline is blocked by the target, times out, or encounters an internal error cost 0 credits.
No. Tapline is independent. Tapline returns publicly available data.
Start with X (Twitter) data.
Try the live demo. Sign up for 100 free credits when you are ready.