Development and APIs

New version for Writing Data into UPC CMS

6 Feb 2017

New version of the API has been added.

The old API is still available at
It will be removed on the next release, and proprietor and spc data are not saved anymore.

The new API is available at

This swagger file contains the new definition.

Major changes:

  • revised SPC and SPC holder data
  • revised proprietor (same format as SPC holder)
  • new country indications (addresses.state and SPCData.nationalDesignation), must be encoded with ISO 3166-1 alpha-2
  • new endpoint /nationalDesignation (to get a list of national designations for SPC and proprietor. It contains dummy data; it will be a complete list with the next release
  • SpcData.nationalDesignation and Proprietor.nationalDesignation must comply with the list returned from /nationalDesignation
  • moved some check to early stage for feedback in case of input error ( must be well formed, etc)
  • added officialCaseNumber at CaseResult
  • added CaseResult to the ErrorResponse. It will help to track the case in error, by case number.

There is no need to generate another key code.

Accessing Data from UPC

Public APIs are available for accessing public data in the CMS. These include:

  • /caseTypes for a list of case types
  • /cases for searching the cases
  • /document for obtaining and downloading a list of documents related to a case

Detailed descriptions of APIs and parameters are in this Swagger file:

The current URL for accessing the APIs is:

[deprecated] Writing Data into UPC CMS

Public APIs are available for writing data into the CMS. Current APIs allow for the following applications:

Submit Opt Out and Withdraw Applications

Detailed descriptions of the APIs and their parameters are in this Swagger file:

The current URL for accessing the APIs is:

To use this functionality, a user App must be created and authorised. In order to do this:

  • Log into the UPC CMS, access the new "My Developer App" menu on the left panel and create an application
  • A Client secret key will be displayed and saved in the private area, to be used for authenticating all API calls
  • The secret key must be added in the header of all calls, named "X-API-KEY"
  • This swagger file describes all parameters and returned data