Download OpenAPI specification:Download
This describes the resources that make up the Eclipse Project Management Infrastructure (PMI) REST API. You can contribute to this document via our git repository. If you have any problems or requests please submit an issue.
This API currently limits users to 1000 authenticated requests and 1000 anonymous requests an hour.
Information about pagination is provided in the Link header of an API call. For example, let’s make a curl request to the eclipse_profile API, to find out how many org_eclipse_oomph records exist for the user:
curl -I \"https://projects.eclipse.org/api/projects?page=1&pagesize=20\"
The -I parameter indicates that we only care about the headers, not the content. In examining the result, you’ll notice some information in the Link header that looks like this:
<https://projects.eclipse.org/api/projects?page=2&pagesize=2>; rel="next",
<https://projects.eclipse.org/api/projects?page=27&pagesize=2>; rel="last",
<https://projects.eclipse.org/api/projects?page=1&pagesize=2>; rel="first",
<https://projects.eclipse.org/api/projects?page=1&pagesize=2>; rel="self"
Let’s break that down. rel="next" says that the next page is page=2. This makes sense, since by default, all paginated queries start at page 1. rel="last" provides some more information, stating that the last page of results is on page 27. Keep in mind that you should always rely on these link relations provided to you. Don’t try to guess or construct your own URL.
The common HTTP Response Status Codes are used.
Eclipse Projects are available through this resource. Note that it is available through the https://projects.eclipse.org domain.
Retrieve metadata for all projects.
github_only | integer <int32> Select only the projects that contains GitHub repos |
spec_project | integer <int32> The index of the page to get, defaults to 1. |
spec_project_working_group | string The index of the page to get, defaults to 1. |
working_group | string The index of the page to get, defaults to 1. |
page | integer <int32> The number of records to get per page, defaults to 20. Maximum value is 100. |
pagesize | integer <int32> The number of records to get per page, defaults to 20. Maximum value is 100. |
order_by | string The order by name in which the results will be returned. ASC by default |
[- {
- "project_id": "ee4j.batch",
- "name": "Jakarta Batch",
- "scope": "<p><strong>Project Scope: </strong>The Jakarta Batch project defines and maintains the Jakarta Batch specification and related artifacts.</p>\n<p><strong>Specification Scope: </strong> Jakarta Batch describes a means for developing, executing and managing batch processes in Jakarta EE applications.</p>\n\n",
- "logo": "",
- "github_repos": [
], - "contributors": [ ],
- "committers": [
], - "working_groups": [
- {
- "name": "Jakarta EE",
- "id": "jakarta-ee"
}
], - "spec_project_working_group": {
- "name": "Jakarta EE",
- "id": "jakarta-ee"
}
}
]
Retrieve information for a specific project
Note that every dots in a project id needs to be changed to an underscore
project_id required | string ID of the project. |
[- {
- "project_id": "ee4j.batch",
- "name": "Jakarta Batch",
- "scope": "<p><strong>Project Scope: </strong>The Jakarta Batch project defines and maintains the Jakarta Batch specification and related artifacts.</p>\n\n\n<p><strong>Specification Scope: </strong> Jakarta Batch describes a means for developing, executing and managing batch processes in Jakarta EE applications.</p>\n\n",
- "logo": "",
- "github_repos": [
], - "contributors": [ ],
- "committers": [
], - "working_groups": [
- {
- "name": "Jakarta EE",
- "id": "jakarta-ee"
}
], - "spec_project_working_group": {
- "name": "Jakarta EE",
- "id": "jakarta-ee"
}
}
]