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 Delete Request API

User delete request processing

Eclipse Foundation User Delete Request 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 Delete Request. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, an API reference, and a changelog.

This API exposes 6 operations across 4 paths, and defines 5 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.

6 operations 4 paths 5 schemas 1 DELETE3 GET1 POST1 PUT

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 Delete Request API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow, exposing 1 scope.

Paths & Operations 6

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

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

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are UserDeleteRequest (9 properties), PaginatedUserDeleteRequests (2 properties), RequestStatusUpdate (1 property). Each schema is shown below with its type and property counts.

PaginatedUserDeleteRequests
object
2 properties 2 required
Error
array
An array containing a single message indicating the error
UserDeleteRequest
object
9 properties 9 required
RequestStatusUpdate
object
1 property 1 required
UserDeleteRequests
array
The list of UserDeleteRequest objects found

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eclipse-user-delete-request-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 Delete Request 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.