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, and new accounts start with 100 free requests to test all 40 endpoints (no card required). 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 and following lists, and account metadata. Related guides: Followers & Following | Audience Geography | Competitor Analysis

Tweets

Endpoints for retrieving tweet content, engagement metrics, replies, quotes, retweeters, long-form articles, and trending topics. Related guides: Search Tweets | Tweet Engagement | X Articles | Historical Data
Endpoints for searching tweets, mentions, and user profiles, and for looking up X Spaces. 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. Related guide: Marketing Campaign Verification

Community

Endpoints for accessing X Community data: member lists, tweet feeds, and in-community search. Related guide: Lists & Communities

Lists

Endpoints for accessing X List data: member profiles, list subscribers, and the combined tweet feed. 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. Accepts username, user_id, or user_link. Related guide: Sorsa Score & Crypto Analytics

Technical Utilities

Endpoints for ID conversion and API key usage monitoring. Related guides: ID Conversion | Pricing

Data Models

Two core objects appear across most endpoints. For full details, including every variant, field type, and edge case, see Response Format.

User Object

Returned by /info and /info-batch, by the follower, following, and user-search endpoints, and embedded in every tweet response as the user field. Some endpoints add fields (for example, follower endpoints include a followerDate); see Response Format for those variants.

Tweet Object

Returned by /tweet-info, /search-tweets, /user-tweets, /comments, /quotes, /mentions, /list-tweets, and community tweet endpoints.

TweetEntity Object


Common Patterns

Authentication: All requests require the ApiKey header. See Authentication. Pagination: Endpoints returning lists use cursor-based pagination. Pass the next_cursor 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": "..." } on errors (400, 401, 403, 404, 429, 500). See Error Codes. Rate limit: 20 requests per second on all standard 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