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

REST API for Eclipse account profiles and user metadata, including the two-phase user deletion request flow the Foundation operates for data-protection erasure requests.

Eclipse Profile 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 Accounts, Identity, Privacy, and Profile. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 15 operations across 13 paths, organized into 4 resource areas, and defines 22 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.

15 operations 13 paths 22 schemas 2 DELETE10 GET2 POST1 PUT

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
Authentication
OAuth 2.0
Resource Areas
4

Authentication & Security 1

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

Paths & Operations 15

Across 13 paths, the API surfaces 15 operations — 2 DELETE, 10 GET, 2 POST, 1 PUT. They span 4 resource areas: User Profile, User Metadata, User Delete Request, Slack Webhook. 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
User Metadata 4

Additional user metadata

GET
/account/profile/{name}/eca
Retrieve user eca status via username
RetrieveEca 1 param → 200500
GET
/account/profile/{name}/employment-history
Retrieve user employment history via username
getUserEmploymentHistory 1 param → 200500
GET
/account/profile/{name}/mailing-list
Retrieve user mailing-list subscriptions via username
RetrieveMailingList 1 param → 200404500
GET
/account/profile/{name}/projects
Retrieve user projects via username
RetrieveProjects 1 param → 200404500
User Delete Request 6

User delete request processing

POST
/account/profile/{name}/user_delete_request
Initialize the user deletion process via username
CreateDeleteRequests 1 param → 201403404409500
GET
/account/user_delete_request
Retrieve list of user delete requests via params
RetrieveDeleteRequests 7 params → 200500
GET
/account/user_delete_request/ready
Retrieve list of final-stage user delete requests
RetrieveFinalStageDeleteRequests → 200204500
GET
/account/user_delete_request/{request_id}
Retrieve a user delete request by id
RetrieveDeleteRequest 1 param → 200403404500
PUT
/account/user_delete_request/{request_id}
Update a user delete request by id
UpdateDeleteRequest 1 param body → 204400403404500
DELETE
/account/user_delete_request/{request_id}
Delete a user delete request by id
DeleteDeleteRequest 1 param → 204403404500
Slack Webhook 1

Slack Webhook processing

POST
/slack/profile
Retrieve a user profile by username or email.
SlackProfileWebhook body → 200403500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are UserData (31 properties), UserDeleteRequest (9 properties), PeopleProject (8 properties), EmploymentHistory (4 properties). Each schema is shown below with its type and property counts.

UserDatas
array
UserData
object
31 properties 12 required
Eca
object
2 properties 2 required
Country
object
2 properties
PublisherAgreement
object
1 property 1 required
Error
array
An array containing a single message indicating the error
ExtendedError
object
An object with a status code and message denoting an upstream error
3 properties 2 required
Subscriptions
object
1 property 1 required
EmploymentHistories
array
EmploymentHistory
object
4 properties 3 required
MailingList
object
2 properties 2 required
PeopleProjectMap
object
PeopleProjects
array
Map of projects that the user is associated with.
PeopleProject
object
8 properties 7 required
Relation
object
4 properties 4 required
PaginatedUserDeleteRequests
object
2 properties 2 required
UserDeleteRequests
array
The list of UserDeleteRequest objects found
UserDeleteRequest
object
9 properties 9 required
RequestStatusUpdate
object
1 property 1 required
SlackRequest
object
3 properties 3 required
SlackResponse
object
3 properties 2 required
SlackAttachment
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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