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 Mailing List API

REST API for Eclipse Foundation mailing list metadata and subscription records, authenticated against the auth.eclipse.org foundation realm.

Eclipse Foundation Mailing List 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 Community, Foundations, and Mailing Lists. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 8 operations across 8 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.eclipse.org/foundation/mailing-list, https://api.eclipse.org.

8 operations 8 paths 7 schemas 8 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.eclipse.org/foundation/mailing-list
Authentication
OpenID Connect, OAuth 2.0
Resource Areas
1

Authentication & Security 2

Eclipse Foundation Mailing List API declares 2 security schemes for authenticating requests. It supports OpenID Connect (openId) discovered at https://auth.eclipse.org/auth/realms/foundation/.well-known/openid-configuration. 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 8

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

Mailing Lists 8

Definitions in relation to retrieval of mailing lists

GET
Mailing Lists
getRoot 1 param → 200404500
GET
/available
Available Mailing Lists
getAvailable → 200500
GET
/{listName}
Mailing List
getByListName 1 param → 200404500
GET
/projects
Projects Mailing Lists
getProjects → 200500
GET
/projects/available
Available Projects Mailing Lists
getProjectsAvailable → 200500
GET
/projects/{projectID}
Project Mailing Lists
getProjectsByProjectID 1 param → 200500
GET
/foundation/mailing-list
Fetch Mailing lists
FetchMailingLists 4 params → 200
GET
/foundation/mailing-list/{mailing_list_id}
Retrieve Mailing List
RetrieveMailingList 2 params → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are MailingList (16 properties), FetchMailinglistsresponse (10 properties), RetrieveMailingListresponse (10 properties). Each schema is shown below with its type and property counts.

MailingLists
array
NullableString
nullstring
A nullable String type value
DateTime
string
Date string in the RFC 3339 format. Example, 1990-12-31T15:59:60-08:00. More on this standard can be read at https://tools.ietf.org/html/rfc3339.
MailingList
object
16 properties 8 required
MailingListMapping
object
RetrieveMailingListresponse
object
10 properties 10 required
FetchMailinglistsresponse
object
10 properties 10 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eclipse-mailing-lists-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 Profile API
Eclipse Working Groups API
Eclipse Project Adopters API
Eclipse Foundation Admin API
Where this information came from

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