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

Eclipse Foundation User API

The user-api API from Eclipse Foundation — 19 operation(s) for user-api.

Eclipse Foundation User API is one of 77 APIs that Eclipse Foundation publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User API. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, an API reference, and a changelog.

This API exposes 19 operations across 19 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 0.1.

Requests are made against a single base URL, https://open-vsx.org.

19 operations 19 paths 27 schemas 12 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1
Base URL
https://marketplace.eclipse.org
Terms of Service
Resource Areas
1

Paths & Operations 19

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

User API 19
POST
/user/token/delete/{id}
Delete access token
deleteAccessToken 1 param → 200429
POST
/user/token/create
Create access token
createAccessToken 1 param → 200429
POST
/user/publisher-agreement
Sign publisher agreement
signPublisherAgreement → 200429
POST
/user/namespace/{namespace}/role
Set namespace member
setNamespaceMember 4 params → 200429
POST
/user/namespace/{namespace}/details
Update namespace details
updateNamespaceDetails body → 200429
POST
/user/namespace/{namespace}/details/logo
Update namespace details logo
updateNamespaceDetailsLogo 1 param body → 200429
POST
/user/extension/{namespaceName}/{extensionName}/delete
Delete extension
deleteExtension 2 params body → 200429
GET
/user
Get user data
getUserData → 200429
GET
/user/tokens
Get access tokens
getAccessTokens → 200429
GET
/user/search/{name}
Get users start with
getUsersStartWith 1 param → 200429
GET
/user/namespaces
Get own namespaces
getOwnNamespaces → 200429
GET
/user/namespace/{name}/members
Get namespace members
getNamespaceMembers 1 param → 200429
GET
/user/extensions
Get own extensions
getOwnExtensions → 200429
GET
/user/extension/{namespaceName}/{extensionName}
Get own extension
getOwnExtension 2 params → 200429
GET
/user/customers
Get own customers
getOwnCustomers → 200429
GET
/user/customers/{name}/usage
Get own usage stats
getOwnUsageStats 2 params → 200429
GET
/user/csrf
Get csrf token
getCsrfToken → 200429
GET
/user/auth-error
Get auth error
getAuthError → 200429
GET
/login-providers
Login
login → 200429

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are SearchEntry (15 properties), NamespaceDetails (12 properties), AccessTokenJson (11 properties), TierJson (9 properties). Each schema is shown below with its type and property counts.

NamespaceDetails
object
Details of a namespace
12 properties 3 required
LoginProvidersJson
object
4 properties
NamespaceMembershipJson
object
3 properties
UsageStatsJson
object
3 properties
Extension
Metadata of an extension
9 required
ExtensionReference
object
A reference to another extension in the registry
3 properties 3 required
ErrorJson
object
2 properties
Review
object
A review of an extension
4 properties 3 required
VersionTargetPlatformsJson
object
3 properties
User
object
User data
8 properties 1 required
TargetPlatformActive
object
Target platform of an extension version and whether it is active
3 properties
SearchEntry
object
Summary of metadata of an extension
15 properties 7 required
AccessTokenJson
object
11 properties
QueryResult
Metadata query result
2 required
UsageStatsListJson
object
2 properties
CustomerJson
object
7 properties 2 required
CsrfTokenJson
object
5 properties
Badge
object
A badge to be shown in the sidebar of the extension page in the registry
3 properties
NamespaceMembershipList
object
Metadata of a namespace member list
4 properties 1 required
ReviewList
List of reviews of an extension
1 required
ExtensionReplacement
object
Metadata of an extension replacement
2 properties
VersionReference
object
Essential metadata of an extension version
5 properties
Result
object
Generic result indicator
3 properties
Namespace
Metadata of a namespace
2 required
TierJson
object
9 properties 3 required
TargetPlatformVersion
object
Combination of target platform and version of an extension
2 properties 1 required
SearchResult
List of extensions matching a search query
3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eclipse-user-api-api-openapi.yml Raw ↑

Other APIs Eclipse Foundation publishes across the network.

Eclipse Foundation Eclipse Marketplace REST API
Eclipse Foundation Favorites API
Eclipse Foundation Featured API
Eclipse Foundation Node API
Eclipse Foundation Popular API
Eclipse Foundation Recent API
Eclipse Foundation Search API
Eclipse Foundation Taxonomy API
Eclipse Foundation Mailing List API
Eclipse Profile API
Eclipse Working Groups API
Eclipse Project Adopters API
Where this information came from

This is an independent, third-party profile of Eclipse Foundation User 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.