Eclipse Foundation Eclipse USS API
The Eclipse User Storage Service (USS) allows Eclipse projects to store user-specific project information on the Eclipse Foundation servers. The goal is to make it easy for our projects to offer a better user experience by storing relevant information in a central location.The BLOB resource is a way for projects to store binary objects based off a application_token/key value pair.The “value” is always the last element in this JSON structure. All other things must come before that so that the SDK implementation can parse and collect them into a Map and finally return a decoding InputStream to deliver the “value” content back to the caller/application. The blob value is available when the client retrieve a specific blob using an application_token and key.We are using application_token and key to identify a blob. The Application token is a string that is assigned by the Eclipse Management Organization.The key string must respect the following validation rules:* 5-25 characters;* letters: lowercase and uppercase/numbers/underscores are valid;* each string should start with a letter.
Eclipse Foundation Eclipse USS 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 Eclipse USS. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, an API reference, and a changelog.
This API exposes 4 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.
Requests are made against a single base URL, https://api.eclipse.org.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Eclipse Foundation Eclipse USS API declares
1 security scheme
for authenticating requests.
It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 2 scopes.
oauth2— Get access to data while protecting your account credentials. OAuth2 is also a safer and more secure way to give you access.
Paths & Operations 4
Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
The Eclipse User Storage Service (USS) allows Eclipse projects to store user-specific project information on the Eclipse Foundation servers.
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are SearchBlobsresponse (6 properties), FetchBlobsresponse (5 properties), UpdateCreateBlobsresponse (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Eclipse Foundation 12
Other APIs Eclipse Foundation publishes across the network.
This is an independent, third-party profile of Eclipse Foundation Eclipse USS 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.