Skip to main content

Complete API Reference: All Sorsa Endpoints

All Sorsa API endpoints are listed below, organized by category. Every endpoint uses the same base URL (https://api.sorsa.io/v3) and authenticates via the ApiKey header. Every call costs exactly 1 request from your quota regardless of which endpoint you use. For detailed parameter tables, response schemas, and interactive testing, click the Docs link next to each endpoint. You can also test any endpoint without code using the API Playground.

Users Data

Endpoints for retrieving user profiles, follower/following lists, and account metadata.
EndpointMethodDescriptionDocs
/infoGETFull profile for a single account (bio, counts, verified status, avatar). Accepts username, user_id, or user_link.Docs
/info-batchGETProfiles for multiple accounts in one request. Accepts usernames[] or user_ids[].Docs
/aboutGETCountry, username change count, and last change date.Docs
/followersGETPaginated follower list with full profiles. Up to 200 users per page.Docs
/followsGETPaginated following list with full profiles. Up to 200 users per page.Docs
/verified-followersGETPaginated list of only verified followers.Docs
Related guides: Followers & Following | Audience Geography | Competitor Analysis

Tweets

Endpoints for retrieving tweet content, engagement metrics, replies, quotes, retweets, and long-form articles.
EndpointMethodDescriptionDocs
/tweet-infoPOSTFull data for a single tweet (text, metrics, author profile). Body: tweet_link.Docs
/tweet-info-bulkPOSTFull data for up to 100 tweets in one request. Body: tweet_links[].Docs
/user-tweetsPOSTPaginated timeline of a user’s tweets. Body: link or user_id.Docs
/commentsPOSTReplies under a specific tweet. Body: tweet_link.Docs
/quotesPOSTQuote tweets of a specific tweet. Body: tweet_link.Docs
/retweetsPOSTUsers who retweeted a tweet (returns user profiles, not tweets). Body: tweet_link.Docs
/articlePOSTFull content of an X Article (long-form post). Body: tweet_link.Docs
Related guides: Search Tweets | Tweet Engagement | X Articles | Historical Data
Endpoints for searching tweets, mentions, and user profiles by keyword.
EndpointMethodDescriptionDocs
/search-tweetsPOSTSearch tweets by keyword with full X operator support. Body: query, order, next_cursor.Docs
/mentionsPOSTTweets mentioning a specific handle, with engagement and date filters. Body: query, order, min_likes, min_retweets, min_replies, since_date, until_date.Docs
/search-usersPOSTSearch user profiles by keyword (matches bios, display names, handles). Body: query.Docs
Related guides: Search Tweets | Track Mentions | Search Operators | Target Audience Discovery

Verification

Endpoints for checking whether a user performed a specific action (follow, retweet, comment, quote, community membership). Designed for campaign and giveaway verification.
EndpointMethodDescriptionDocs
/check-followPOSTDid a user follow a specific account? Body: project_handle/project_id + username/user_link/user_id.Docs
/check-commentGETDid a user comment on a specific tweet? Returns the comment tweet if found. Query: tweet_link + user_handle/user_id.Docs
/check-retweetPOSTDid a user retweet a specific tweet? Checks up to 100 retweets per request. Body: tweet_link + user identifier.Docs
/check-quotedPOSTDid a user quote a specific tweet? Returns status: quoted, retweet, or not_found. Body: tweet_link + user identifier.Docs
/check-community-memberPOSTIs a user a member of a specific X Community? Body: community_id + user identifier.Docs
Related guide: Marketing Campaign Verification

Community

Endpoints for accessing X Community data: member lists, tweet feeds, and in-community search.
EndpointMethodDescriptionDocs
/community-tweetsPOSTTweet feed from a community. Body: community_id, order_by.Docs
/community-search-tweetsPOSTSearch tweets within a community by keyword. Body: community_link, query, order_by.Docs
/community-membersPOSTMember list of a community with full profiles. Body: community_link.Docs
Related guide: Lists & Communities

Lists

Endpoints for accessing X List data: member profiles, list subscribers, and the combined tweet feed.
EndpointMethodDescriptionDocs
/list-membersGETProfiles of accounts in a list. Query: list_id.Docs
/list-followersGETProfiles of users who follow a list. Query: list_link.Docs
/list-tweetsGETRecent tweets from all list members. Query: list_id.Docs
Related guides: Lists & Communities | Real-Time Monitoring

Sorsa Score (Crypto Analytics)

Endpoints for crypto-specific analytics: influence scoring, follower categorization, and recent follow activity among crypto accounts in Sorsa’s database.
EndpointMethodDescriptionDocs
/scoreGETCurrent Sorsa Score (crypto influence metric). Query: link/username/user_id.Docs
/score-changesGETScore delta over the last week and month.Docs
/followers-statsGETFollower breakdown: influencers, projects, VCs.Docs
/top-followersGETTop 20 followers ranked by Sorsa Score.Docs
/top-followingGETTop 20 followed accounts ranked by Score.Docs
/new-followers-7dGETCrypto accounts that followed in the last 7 days.Docs
/new-following-7dGETCrypto accounts the user started following in the last 7 days.Docs
Related guide: Sorsa Score & Crypto Analytics

Technical Utilities

Endpoints for ID conversion and API key usage monitoring.
EndpointMethodDescriptionDocs
/username-to-id/{handle}GETConvert a username to a permanent User ID.Docs
/id-to-username/{user_id}GETConvert a User ID to the current username.Docs
/link-to-idGETExtract User ID from a profile URL. Query: link.Docs
/key-usage-infoGETCurrent request usage, remaining quota, and expiration date. No parameters.Docs
Related guides: ID Conversion | Pricing

Data Models

Two core objects appear across all endpoints. For full details including field types and edge cases, see Response Format.

User Object

Returned by /info, /followers, /follows, /search-users, and embedded in every tweet response as the user field.
FieldTypeDescription
idstringPermanent User ID (Snowflake)
usernamestringCurrent handle
display_namestringDisplay name
descriptionstringBio text
locationstringSelf-reported location
created_atstringAccount creation date
followers_countintegerFollower count
followings_countintegerFollowing count
favourites_countintegerTotal likes given
tweets_countintegerTotal tweets posted
media_countintegerMedia posts count
verifiedbooleanVerification status
protectedbooleanProtected (private) account
can_dmbooleanDMs open
possibly_sensitivebooleanSensitive content flag
profile_image_urlstringAvatar URL
profile_background_image_urlstringBanner image URL
bio_urlsstring[]URLs extracted from bio
pinned_tweet_idsstring[]IDs of pinned tweets

Tweet Object

Returned by /tweet-info, /search-tweets, /user-tweets, /comments, /quotes, /mentions, /list-tweets, and community tweet endpoints.
FieldTypeDescription
idstringTweet ID (Snowflake)
full_textstringComplete tweet text
created_atstringPost timestamp
langstringLanguage code
likes_countintegerLikes
retweet_countintegerRetweets
reply_countintegerReplies
quote_countintegerQuotes
bookmark_countintegerBookmarks
view_countintegerViews
conversation_id_strstringThread/conversation ID
in_reply_to_tweet_idstringParent tweet ID (if reply)
in_reply_to_usernamestringParent author (if reply)
is_replybooleanWhether this is a reply
is_quote_statusbooleanWhether this is a quote tweet
is_replies_limitedbooleanReplies restricted by author
userUserComplete author profile
entitiesTweetEntity[]Attached media entities
quoted_statusTweetNested quoted tweet (if quote)
retweeted_statusTweetNested retweeted tweet (if RT)

TweetEntity Object

FieldTypeDescription
typestringEntity type
linkstringEntity URL
previewstringPreview text

Common Patterns

Authentication: All requests require the ApiKey header. See Authentication. Pagination: Endpoints returning lists use cursor-based pagination. Pass next_cursor (or cursor for some GET endpoints) from the previous response to fetch the next page. When the cursor is absent or null, you have reached the end. See Pagination. Error format: All endpoints return { "message": "..." } for 400, 403, 404, and 500 errors. See Error Codes. Rate limit: 20 requests per second on all plans. See Rate Limits. Input flexibility: Most user-related endpoints accept three input formats: username, user_id, or user_link (profile URL). Provide exactly one.

Next steps