API Documentation
|
where {localeCode}
is a supported locale code.
GET
- retrieves the contents of an internationalization (i18n) bundle (specified by localeCode
) as key/value pairs in JSON format.POST
- uploads a custom i18n locale bundle (for localeCode
) to the Cocoon Data Platform's Access Service.Note: The
GET
method takes no parameters.
This API endpoint serves a number of purposes:
{localCode}
) as key/value pairs in JSON format.localeCode
) to the Cocoon Data Platform's Access Service.This API endpoint supports requests utilizing Cocoon Data user accounts with the following roles (as described in the SafeShare Administrator's and Organisation Administrator's Guides):
GET
method.POST
method.The Cocoon Data Platform's resources available to a Cocoon Data user meeting the criteria above is determined by the access token submitted in the header of requests to this endpoint.
The appropriate access token as the Bearer
token:
Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJleHAiOjE0NjcwMTY2NjYsInVzZXJfbmFtZSI6ImFsZXgub...
The following header is also required in a POST request to allow multi-part (including binary) form data elements to be uploaded through the request:
Content-Type: multipart/form-data
Note: It is also worth appending to this header a
boundary
parameter, whose string value is used to demarcate each multi-part form data element of the request (i.e. this string is not used for any other purpose throughout the entire request).
For example, to use the following string to demarcate each multi-part form data element:
-----------------------------12345678901234567890123456
assign this string value to theboundary
parameter, which in turn is appended to theContent-Type: multipart/form-data
header, such that this header will be:
Content-Type: multipart/form-data; boundary=-----------------------------12345678901234567890123456
The following required parameter must be sent in the body of the POST request, as an individual multi-part form data elements:
If the request succeeded, then an HTTP response status 200 OK
is returned.
For successful requests only, a JSON-formatted response containing the following members is also returned:
If the request succeeded, then an HTTP response status 200 OK
is returned.
For successful requests only, a JSON-formatted response containing the following members is also returned: