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 Open VSX Publisher Agreement API

REST API for submitting and revoking the Eclipse Open VSX publisher agreement against an Eclipse account, gated by the openvsx_publisher_agreement OAuth scope.

Eclipse Open VSX Publisher Agreement API is one of 26 APIs that Eclipse Foundation publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Agreements, Legal, Open VSX, and Publishing. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 5 operations across 3 paths, organized into 2 resource areas, and defines 8 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://api.eclipse.org/openvsx.

5 operations 3 paths 8 schemas 1 DELETE3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.eclipse.org/openvsx
Authentication
OAuth 2.0
Resource Areas
2

Authentication & Security 1

Eclipse Open VSX Publisher Agreement API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 4 scopes.

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 1 DELETE, 3 GET, 1 POST. They span 2 resource areas: Publisher Agreement, Profile. Each is listed below with its method, path, parameters, and response codes.

Publisher Agreement 4
GET
/publisher_agreement
Publisher Agreement
→ 200404500
POST
/publisher_agreement
Create a Publisher Agreement
body → 200400409500
GET
/publisher_agreement/{ef_username}
Publisher Agreement for specific user
1 param → 200404500
DELETE
/publisher_agreement/{ef_username}
Delete Publisher Agreement for specific user
1 param → 204404500
Profile 1
GET
/profile
User profile
→ 200403500

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are EfUser (26 properties), PublisherAgreement (10 properties), Error (4 properties), Eca (2 properties). Each schema is shown below with its type and property counts.

PublisherAgreement
object
10 properties 9 required
AgreementSigningRequest
object
2 properties 2 required
Error
object
4 properties 2 required
EfUsers
array
EfUser
object
26 properties
Eca
object
2 properties
Country
object
2 properties
ProfilePublisherAgreement
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eclipse-openvsx-api-openapi.yml Raw ↑

Other APIs Eclipse Foundation publishes across the network.

Eclipse Marketplace API
Eclipse Foundation Web API
Eclipse Projects API
Open VSX Registry API
Eclipse Newsroom REST API
Eclipse Foundation Eclipse Marketplace REST API 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
Where this information came from

This is an independent, third-party profile of Eclipse Open VSX Publisher Agreement 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.