A client can allow end-users to add a package to APS Catalog with one of the following methods:
This chapter explains how to build this capability into a client.
In this document:
The sequence of actions performed by a client and a user to add a package to APS Catalog is as follows:
Packages uploaded through the APS Catalog form are enabled by default.
For details on form fields (HTTP POST arguments) and possible APS Catalog responses, refer to ADD Package in the API Reference.
Adding and removing a Package is is also possible through submitting an HTML POST request to either of the following URL’s:
For details on POST arguments and possible APS Catalog responses, see APS Catalog Form Arguments.
Submitting a rating and review for an application is possible through an HTTP POST request. The rating is submitted for a certain package and is applied to all other packages of the application. The new vote is added to the existing rating and averaged out. You may see the average rating (as well as the total number of votes) in Application and Application Version feeds, see Feeds for details.
The POST request has to be sent to the following URL:
The placeholder string means the following:
The details on POST arguments and possible APS Catalog responses see below:
||Name of application package||string||yes|
||Name of package vendor||string||yes|
||Package version and release||string||yes|
|200 Ok||Review has been successfully uploaded to the repository.|
|400 Bad request||The submitted request is incomplete and cannot be accepted. Check whether all required arguments are sent|
|401 Unauthorized||Authorization required. Username or password is incorrect.|
|405 Method not allowed||The handler does not accept the request method. Only the POST method is accepted.|