- 1 Eclipse Marketplace REST API Documentation
- 1.1 Provisional API
- 1.2 Retrieving a listing of all catalogs
- 1.3 Retrieving A listing of Markets and Categories
- 1.4 Retrieving a set of listings from a specific Market / Category
- 1.5 Returning a Specific Listing
- 1.6 Returning Search Results
- 1.7 Featured Listings
- 1.8 Recently Updated Listings
- 1.9 Top Favorited Listings
- 1.10 Most Popular Listings
- 2 Catalogs
- 3 Marketplace Client
Eclipse Marketplace REST API Documentation
The Eclipse Marketplace API is currently in a provisional state. The URLs for the API calls may change at any time.
This provisional API is identified by 'api/p' at the end of most URLs.
One of the goals of the API that is to make it very simple for someone to figure out how to use the API by using the website. If you add the /api/p to the websites url it should return the equivalent data in an XML response.
Retrieving a listing of all catalogs
This will return a listing of all catalogs that are browsable with the MPC. It also includes basic branding parameters, like title and icon and strategies resolving dependencies. If you want to override this url (e.g. in your RCP application) you have to set the following system-property:
This setting will request the url
http://mydomain.tld/catalogs/api/p to obtain all available catalogs.
Retrieving A listing of Markets and Categories
This will return a listing of Markets and Categories, it includes URLs for each category, as well number of listings in each category.
Retrieving a set of listings from a specific Market / Category
http://markerplace.eclipse.org/taxonomy/term/[category id],[market id]/api/p
This call returns a set of listings that correspond to the category / market specified.
Example: If you wanted to return the XML for all Build and Deploy Listings in the Tools Market you would use this call.
These urls are easily obtained from using the http://marketplace.eclipse.org/api/p call.
Returning a Specific Listing
There are two methods of returning a specific listing.
Calls to either URL will return a listing of contents of a node.
- You will need to supply the value in the URL for [title] or [node id]. These URLS will be provided in full by queries to return a subset of listings such as Categories, Searches, Featured etc.
- Most fields in the XML document are self explanitory. However there are a few fields that require explanation.
- Type - this is the type of listing being returned. 'training' is for a Training and Consulting Listing, 'resource' is for a solutions listing.
- Body - this field can and most likely contains HTML markup. This also applies to the Training and Consulting Fields (trainingdesc and consultingdesc)
- Created - this field is when the listing was first created. It is the number of seconds since the epoch. See http://us.php.net/manual/en/function.time.php for more details.
- Changed - this field is the last time this listing was changed. It is the number of seconds since the epoch. See http://us.php.net/manual/en/function.time.php for more details.
- FoundationMember - this is a boolean field. 0 meaning No, 1 meaning Yes.
- example: http://marketplace.eclipse.org/node/51/api/p will return a Training and Consulting Listing
- example: http://marketplace.eclipse.org/content/subclipse/api/p will return a Solutions Listing.
Returning Search Results
There is one exception to using the api/p at the end of URLs. The search API needs this string to be at the start of the URL.
[query] - This is the string you wish to query the database with
[page num] - The search API returns 10 results per page. Use this parameter to iterate though pages. The root node will always return the total number of results.
[filters] - There are 3 different filters used by the Apache Solr search database that can be used to constrain (Facet) your searches. If you plan to use more then one filter they must be SPACE separated.
- tid - This field is the database equivalent of category IDs.
Example : http://marketplace.eclipse.org/api/p/search/apachesolr_search/enterprise?filters=tid:9 tid:31 This query would search for 'Enterprise' in the J2EE category of the Tools Market.
- ss_cck_field_status - this filter is the equivalent of the <status> tag in a listings XML result.
Example : http://marketplace.eclipse.org/api/p/search/apachesolr_search/enterprise?filters=ss_cck_field_status:Production%2FStable This query would search for 'Enterprise' listings that have a Status matching 'Production/Stable'
- ss_cck_field_licensetype - this filter is the equivalent of the <license> tag in the listings XML result.
Example : http://marketplace.eclipse.org/api/p/search/apachesolr_search/enterprise?filters=ss_cck_field_licensetype:'Free EPL' This query would search for 'Enterprise' listings that have a License Type matching "Free EPL".
This call will return a list of Featured Listings. By default this returns 6 listings. The default is configured on the server.
This call will return a list of featured listings constrained by a category / market id (or both). By default this returns 6 listings. The default is configured on the server.
- http://marketplace.eclipse.org/featured/2/api/p - This call will return featured items from the Code Management (ID = 2) Category.
- http://marketplace.eclipse.org/featured/31/api/p - This call will return featured items from the Tools (ID = 31) Market.
- http://marketplace.eclipse.org/featured/2,31/api/p - This call will return featured items that are contained in both the Code Management and Tools categories.
Recently Updated Listings
This call will return a list of Recently Updated or Added Listings. By default this returns 6 listings. The default is configured on the server.
Top Favorited Listings
This call will return a list of the Most Favorited Listings. By default this returns 6 listings. The default is configured on the server.
Most Popular Listings
This call will return a list of Most Popular listing by activity. By default this returns 6 listings. The default is configured on the server.
What is a Catalog
A catalog is an HTTP service which returns XML data back to the Marketplace Client from. Currently Marketplace uses PHP with an SQL backend to serve these pages to the MPC.
Building a Catalog
In terms of building your own catalog with this data you would follow a three step process.
- Query the Base URL for a listing of Markets and their categories.
- Iterate through that query to retrieve listings for each category using the Category URL.
- Finally iterate through the Category Query to retrieve the data related to each node.
The Marketplace Client (MPC) project implements a client to the REST API. Though the client does not provide public Java API for accessing the REST API, it may be useful for testing purposes when building a catalog.
Of interest to catalog providers or implementors of client libraries to access the REST API in MPC:
- /org.eclipse.epp.mpc.core/mpc-rest.xsd An XML Schema that describes the REST API data format
org.eclipse.epp.internal.mpc.core.service.DefaultMarketplaceServiceA Java class that provides a Java API to the REST service
org.eclipse.epp.mpc.tests.service.DefaultMarketplaceServiceTestA JUnit test case that exercises the REST API