Get Account Registration and Usage Context
View all X (Twitter) Public Data API endpoints →Pass required screenname to retrieve the available registration and usage information associated with a public X profile. This contextual read complements the ordinary user-info profile lookup; it must not be used as proof of a person's location, identity or account ownership. No response sample has been live-verified for this endpoint, so exact metadata keys, historical depth and missing-account behavior are not established. Preserve absent information instead of inventing account-history details.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/twitter/about-profile API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/twitter/about-profile?key=<API_KEY>&screenname=elonmusk'
Query Result
Use Cases
- Add available registration context to an editorial public-account directory alongside its ordinary profile record.
- Give an analyst a supplementary account-context panel without converting metadata into an identity-verification score.
- Review missing registration metadata separately from unavailable profile data during a directory-quality audit.
- Compare the account context actually returned across institutional handles while documenting unverified field coverage.
Frequently asked questions
What is about-profile used for?
It requires screenname and requests available account registration and usage context, separately from the ordinary biography and counts supplied by user-info. Exact metadata fields and historical depth still require response validation.
Can this account context verify location or ownership?
No. Registration and usage metadata is not proof of physical location, legal identity or account control. Preserve absent context instead of inferring account-history events.