Batch Twitter Profile Lookup API

Submit required rest_ids as a comma-separated string of numeric X account IDs. This read is described as returning an array of user profiles for the supplied IDs. Preserve each ID as a string and join records by returned identifiers rather than assuming response order, one result per input or a fixed batch limit. This endpoint has not been live-verified: exact profile fields, accepted batch sizes and unavailable-account behavior require validation before production parsing. Use user-info when a single handle lookup and its observed active/notfound contract are sufficient.

API Features

Comma-separated account-ID input rest_ids accepts the documented string-list format rather than a JSON request body.

Profile refresh by stable identifiers Numeric account IDs provide a handle-independent lookup key for refreshing a saved public-account directory.

Batch coverage validation The catalog describes an array of users; verify partial results and unavailable IDs instead of assuming complete positional output.

Undocumented batch ceiling No accepted maximum was observed, so test manageable batches before selecting an ingestion batch size.

Live API Demo

GET /api/project/twitter/profiles-by-rest-ids

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/twitter/profiles-by-rest-ids?key=<API_KEY>&rest_ids=44196397%2C34743251'

curl -X GET 'https://api.opendata-api.com/api/project/twitter/profiles-by-rest-ids?key=<API_KEY>&rest_ids=44196397%2C34743251'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Refresh saved numeric account IDs after an observed handle change without creating a duplicate directory entry.
Enrich deduplicated public account IDs collected from reposter pages in validated-size batches.
Reconcile an institutional account directory against the available profiles returned for its persisted IDs.
Measure observed batch coverage for a research import and queue missing IDs for a separate review.

Frequently asked questions

How should I format a batch profile lookup?

Send required rest_ids as a comma-separated string of numeric account IDs. Preserve IDs as strings and join returned profiles by identifier rather than response position. No accepted maximum batch size has been verified.

Will every supplied account ID return a profile?

Complete per-input coverage and unavailable-account behavior have not been live-verified. Validate manageable batches and keep missing IDs separate from returned records; user-info provides a demonstrated active/notfound contract for a single handle.

Related operations

Guides

View Subscription Plans →

Look Up Multiple Profiles by Account IDs