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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Eclipse Foundation

Eclipse Foundation Registry API

The registry-api API from Eclipse Foundation — 25 operation(s) for registry-api.

Documentation Provider Profile APIs.io OpenAPI GitHub

Eclipse Foundation Registry 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 registry-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 26 operations across 25 paths, and defines 21 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.

26 operations 25 paths 21 schemas 21 GET5 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
License
Eclipse Public License 2.0
Terms of Service
View terms
Resource Areas
1

Paths & Operations 26

Across 25 paths, the API surfaces 26 operations — 21 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

registry-api 26
POST
/api/user/publish
Publish an extension by uploading a vsix file
publish body → 201400403429
POST
/api/user/namespace/create
Create a namespace
createNamespace body → 201400403429
GET
/api/-/query
Provides metadata of extensions matching the given parameters
getQuery 10 params → 200400429
POST
/api/-/querydeprecated
Provides metadata of extensions matching the given parameters.
postQuery body → 301429
POST
/api/-/publish
Publish an extension by uploading a vsix file
publish_1 1 param body → 201400401403429
POST
/api/-/namespace/create
Create a namespace
createNamespace_1 1 param body → 201400429
GET
/api/{namespace}
Provides metadata of a namespace
getNamespace 1 param → 200404429
GET
/api/{namespace}/{extension}
Provides metadata of the latest version of an extension
getExtension 2 params → 200404429
GET
/api/{namespace}/{extension}/{version}
Provides metadata of a specific version of an extension
getExtension_1 3 params → 200404429
GET
/api/{namespace}/{extension}/{version}/file/**
Access a file packaged by an extension
getFile 3 params → 200302404429
GET
/api/{namespace}/{extension}/{targetPlatform}
Provides metadata of the latest version of an extension
getExtension_2 3 params → 200404429
GET
/api/{namespace}/{extension}/{targetPlatform}/{version}
Provides metadata of a specific version of an extension
getExtension_3 4 params → 200404429
GET
/api/{namespace}/{extension}/{targetPlatform}/{version}/file/**
Access a file packaged by an extension
getFile_1 4 params → 200302404429
GET
/api/{namespace}/{extension}/{targetPlatform}/versions
Provides a map of versions matching an extension
getVersions 5 params → 200404429
GET
/api/{namespace}/{extension}/{targetPlatform}/version-references
Provides a list of version references matching an extension
getVersionReferences 5 params → 200404429
GET
/api/{namespace}/{extension}/versions
Provides a map of versions matching an extension
getVersions_1 4 params → 200404429
GET
/api/{namespace}/{extension}/version-references
Provides a list of version references matching an extension
getVersionReferences_1 4 params → 200404429
GET
/api/{namespace}/{extension}/reviews
Returns the list of reviews of an extension
getReviews 2 params → 200404429
GET
/api/{namespace}/verify-pat
Check if a personal access token is valid and is allowed to publish in a…
verifyToken 2 params → 200401403404429
GET
/api/{namespace}/logo/{fileName}
Provides logo of a namespace
getNamespaceLogo 2 params → 200404429
GET
/api/{namespace}/details
Get namespace details
getNamespaceDetails 1 param → 200404429
GET
/api/version
Return the registry version
getRegistryVersion → 200404429
GET
/api/v2/-/query
Provides metadata of extensions matching the given parameters
getQueryV2 10 params → 200400429
GET
/api/-/version-changes
[Preview] Provides a paginated feed of the publicly visible transitions of…
getChanges 4 params → 200400429
GET
/api/-/search
Search extensions via text entered by a user
search 8 params → 200400429
GET
/api/-/public-key/{publicId}
Access a public key file
getPublicKey 1 param → 200404429

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are SearchEntry (15 properties), NamespaceDetails (12 properties), QueryParam (10 properties), User (8 properties). Each schema is shown below with its type and property counts.

NamespaceDetails
object
Details of a namespace
12 properties 3 required
VersionReferences
object
List of version references matching an extension
6 properties 3 required
ExtensionReference
object
A reference to another extension in the registry
3 properties 3 required
Extension
Metadata of an extension
9 required
RegistryVersion
object
Configuration of the registry service
5 properties 1 required
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
QueryResult
Metadata query result
2 required
Badge
object
A badge to be shown in the sidebar of the extension page in the registry
3 properties
ReviewList
List of reviews of an extension
1 required
ExtensionReplacement
object
Metadata of an extension replacement
2 properties
QueryParam
object
Parameters of the metadata query
10 properties
VersionReference
object
Essential metadata of an extension version
5 properties
Result
object
Generic result indicator
3 properties
StreamingResponseBody
Namespace
Metadata of a namespace
2 required
Versions
object
Map of versions matching an extension
6 properties 3 required
SearchResult
List of extensions matching a search query
3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Eclipse Foundation publishes across the network.

Eclipse Foundation Eclipse Marketplace REST API
AE Profile APIs.io
Eclipse Foundation Favorites API
AE Profile APIs.io
Eclipse Foundation Featured API
AE Profile APIs.io
Eclipse Foundation Node API
AE Profile APIs.io
Eclipse Foundation Popular API
AE Profile APIs.io
Eclipse Foundation Recent API
AE Profile APIs.io
Eclipse Foundation Search API
AE Profile APIs.io
Eclipse Foundation Taxonomy API
AE Profile APIs.io
Eclipse Foundation Mailing List API
AE Profile APIs.io
Eclipse Profile API
AE Profile APIs.io
Eclipse Working Groups API
AE Profile APIs.io
Eclipse Project Adopters API
AE Profile APIs.io
#registry-api
← Back to E APIs
API Details
ID
eclipse:eclipse-registry-api-api
Base URL
https://marketplace.eclipse.org
Docs
https://marketplace.eclipse.org/
Provider
Eclipse Foundation
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=eclipse-registry-api-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/eclipse-registry-api-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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