Enrich approved accounts: resolve usernames, retain user IDs as strings, request only needed fields, and record retrieval times.
Social Data API
Plan a social-data enrichment and monitoring workflow
Build a bounded workflow for public account enrichment and timeline review, from account selection to refresh and storage decisions.
The available source is currently Twitter / X, not a cross-network social feed. Your application schedules collection and stores results; these endpoints do not provide a managed monitoring subscription.
Built for a specific job
Turn account lookups and timeline pages into a repeatable research dataset.
Collect a bounded timeline: set a page limit and request budget, follow returned cursors, and deduplicate posts by ID in your own storage.
Review changes: distinguish an empty timeline or missing metric from a measured zero; check source freshness before drawing conclusions.
Billing unit
Know how usage is measured
USD per request. Budget for account lookups, every requested timeline page, and later refreshes separately; use the current catalog prices below.
Operational limits
- Use must comply with applicable law and source-platform policies.
- Do not use the service to bypass access controls or perform unauthorized scraping.
- A retrieved timeline is not a complete historical archive or a guarantee of real-time coverage.
- Choose your own retention and deletion policy; do not collect fields that your workflow does not need.
Integration guides
Choose your next step
Current catalog coverage
Available APIs and billing units
Compare API IDs, operations, providers, protocols, and prices. Check the catalog date and each operation's billing unit before estimating usage costs.
Data API
Twitter User Data
twitter-user-data Retrieve public Twitter / X user profiles and user timelines.
- Provider
- Twitter / X Data
- Catalog protocol
- REST
- Billing unit
- request
Published operations
-
GET /v1/twitter/usersGet user by username -
GET /v1/twitter/users/{id}Get user by ID -
GET /v1/twitter/users/{id}/tweetsGet user tweets
Our price
- Request
- $0.0020 /request
Get user by username
GET /v1/twitter/users Our price
- Request
- $0.0020 /request
Get user by ID
GET /v1/twitter/users/{id} Our price
- Request
- $0.0020 /request
Get user tweets
GET /v1/twitter/users/{id}/tweets Our price
- Request
- $0.0020 /request
Request example
Start from the documented operation
curl "https://api.requestbeam.com/v1/twitter/users/<USER_ID>/tweets?max_results=10&tweet.fields=created_at,public_metrics" \
-H "Authorization: Bearer <API_KEY>"const response = await fetch("https://api.requestbeam.com/v1/twitter/users/<USER_ID>/tweets?max_results=10&tweet.fields=created_at,public_metrics", {
headers: { Authorization: "Bearer <API_KEY>" }
});
const data = await response.json();
console.log(data);import requests
url = "https://api.requestbeam.com/v1/twitter/users/<USER_ID>/tweets?max_results=10&tweet.fields=created_at,public_metrics"
headers = {"Authorization": "Bearer <API_KEY>"}
response = requests.get(url, headers=headers, timeout=60)
response.raise_for_status()
print(response.json())Use the API base URL from your account documentation and replace the example placeholders. Send your API key in the Authorization header; never include it in a URL or committed file.