How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Sorsa Community API

Twitter/X Community tweets, members, and community search

Sorsa Community API is one of 8 APIs that Sorsa publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 16 JSON Schema definitions.

Tagged areas include Community. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, rate-limit docs, and 16 JSON Schemas.

This API exposes 3 operations across 3 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 3.0.

Requests are made against a single base URL, https://api.sorsa.io/v3.

3 operations 3 paths 10 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0
Base URL
https://api.sorsa.io/v3
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Sorsa Community API declares 1 security scheme for authenticating requests. An API key is passed in the header as ApiKey (ApiKey). By default, every request must be authenticated.

  • ApiKey — Include your API key in the ApiKey header with every request.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.

Community 3

Twitter/X Community tweets, members, and community search

POST
/community-members
Community Members
body → 200400401403404429500
POST
/community-search-tweets
Search Community Tweets
body → 200400401403404429500
POST
/community-tweets
Community Tweets
body → 200400401403404429500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are common.Tweet (20 properties), common.User (19 properties), common.CommunityUser (6 properties), community.SearchCommunityTweetsReq (4 properties). Each schema is shown below with its type and property counts.

common.User
object
19 properties
common.CommunityUser
object
6 properties
common.TweetEntity
object
3 properties
community.CommunityTweetsReq
object
3 properties 1 required
handler.ErrorResponse
object
1 property
community.CommunityMembersReq
object
2 properties 1 required
community.SearchCommunityTweetsReq
object
4 properties 1 required
common.TweetsResponse
object
2 properties
common.CommunityUsersResponse
object
2 properties
common.Tweet
object
20 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sorsa-community-api-openapi.yml Raw ↑

Other APIs Sorsa publishes across the network.

Sorsa Lists API
Sorsa Search API
Sorsa Sorsa Info Crypto Related API
Sorsa Technical Endpoints API
Sorsa Tweets API
Sorsa Users Data API
Sorsa Verification API
Where this information came from

This is an independent, third-party profile of Sorsa Community API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.