If the Upload File sample given in ODCS documentation is used "as is", we get a http 400 error.
The syntax is strict and every blank line must be empty (no space character for instance).
If we cust and paste the sample, there are residual space characters which must be removed.
So, use this pattern instead:
-----1234567890
Content-Disposition: form-data; name="jsonInputParameters"
{
"parentID": ""
}
-----1234567890
Content-Disposition: form-data; name="primaryFile"; filename="example.txt"
Content-Type: text/plain
Hello World!
-----1234567890--
instead the original one:
The syntax is strict and every blank line must be empty (no space character for instance).
If we cust and paste the sample, there are residual space characters which must be removed.
So, use this pattern instead:
-----1234567890
Content-Disposition: form-data; name="jsonInputParameters"
{
"parentID": "
}
-----1234567890
Content-Disposition: form-data; name="primaryFile"; filename="example.txt"
Content-Type: text/plain
Hello World!
-----1234567890--
instead the original one:
-----1234567890
Content-Disposition: form-data; name="jsonInputParameters"
{
"parentID":"FB4CD874EF94CD2CC1B60B72T0000000000100000001"
}
-----1234567890
Content-Disposition: form-data; name="primaryFile"; filename="example.txt"
Content-Type: text/plain
-----1234567890--
Tests can be conducted from a browser with DHC or POSTMAN or RESTClient.
Commentaires
{
"errorCode": "-97",
"errorMessage": "Content item '(null)' was not successfully checked in. One or more service parameters for service CHECKIN_UNIVERSAL are missing."
}
.documents.us2.oraclecloud.com/documents/api/1.0/files/data
HEADERS section:
Authorization : Your Base64 token
Content-Type : multipart/form-data; boundary=1234567890
BODY section
--1234567890
Content-Disposition: form-data; name="jsonInputParameters"
{"parentID": "F9837651D6C111CFAA80E447C78580E8114D4B29CFDB"
}
--1234567890
Content-Disposition: form-data; name="primaryFile"; filename="helloworld.txt"
Content-Type: text/plain Hello World!
--1234567890--