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 Profile API

Profile data for a user

Eclipse Foundation User Profile 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 Profile. 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 4 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

4 operations 4 paths 6 schemas 1 DELETE3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://marketplace.eclipse.org
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Eclipse Foundation User Profile API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow, exposing 1 scope.

Paths & Operations 4

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

User Profile 4

Profile data for a user

GET
/account/profile
Search for user or get current user
UserSearch 3 params → 200403404500
GET
/account/profile/{name}
Retrieve user via Ef Username
RetrieveUserEf 1 param → 200404500
GET
/github/profile/{handle}
Retrieve user via Github handle
RetrieveUserGh 1 param → 200404500
DELETE
/account/profile/{name}/cache
Clear user profile cache
clearCacheForUser 1 param → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are UserData (31 properties), Country (2 properties), Eca (2 properties), PublisherAgreement (1 property). Each schema is shown below with its type and property counts.

Error
array
An array containing a single message indicating the error
Eca
object
2 properties 2 required
Country
object
2 properties
UserData
object
31 properties 12 required
UserDatas
array
PublisherAgreement
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eclipse-user-profile-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 Profile 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.