Partner API 3.0: Modifying a License Key: Some of provided constants are not resolved

Created:

2017-01-24 08:47:51 UTC

Modified:

2017-08-08 13:41:28 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Partner API 3.0: Modifying a License Key: Some of provided constants are not resolved

Applicable to:

  • Plesk Onyx for Linux

Issue Symptoms

Unable to add feature identifier for existing license using Partner API 3.0:

"code":"400","type":"25216","message":"Some of provided constants were not resolved.","details":"Unresolved constants: \"PLESK-12-DEVELOPER-PACK\"."

Details of the request:

URL: "https://example.com:7050/jsonrest/business-partner/30/keys/10255288?return-key-state=yes" 
Headers: "Accept"=>"*/*; q=0.5, application/xml", "Accept-Charset"=>"UTF-8", "Accept-Encoding"=>"gzip, deflate", "Content-Length"=>"119", "Content-Type"=>"application/json;charset=UTF8"
Payload: "{\"items\":[{\"externalId\":\"12366\",\"item\":\"PLESK-12-WEB-ADMIN-1M\"},{\"externalId\":12366,\"item\":\"PLESK-12-DEVELOPER-PACK\"}]}"

Conditions

Invalid constant PLESK-12-DEVELOPER-PACK in API request.

Resolution

Valid constant for Partner API 3.0 is ADD-PLESK-DEVELOPER-PACK-1M.

Full list of constants valid for Partner API 3.0 is available on the Partner API 3.0 guide.

Have more questions? Submit a request
Please sign in to leave a comment.