Content Management Rest API Call From VBCS Is Failing With 500 Internal Server Error
(Doc ID 2768089.1)
Last updated on AUGUST 24, 2023
Applies to:
Content and Experience Cloud Classic - Version 19.3.2 to 19.3.2Content and Experience Cloud - Version N/A to N/A
Content and Experience Cloud Service - Version N/A to N/A
Information in this document applies to any platform.
Symptoms
The customer is unable to upload digital assets via OCE Content Rest API using end point /content/management/api/v1.1/items via VBCS and is receiving a 500 Internal Server Error in the response.
The Rest API call works fine via Postman (See How To Form The Content Management Rest API Payload In Postman For Creating An Asset? (Doc ID 2763177.1), however fails with the same error with Postman Web.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |