Learn about request and response character set encodings.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
The request body is encoded by the character set in the operation’s resolved request
schema directive. For example, application/json;
charset=ISO-8859-1 encodes the HTTP request in Latin-1 before sending
it to the server.
The response body is encoded by the character set in the operation’s resolved
response schema directive. For example, application/x-www-form-urlencoded; charset=SHIFT_JIS decodes the
percent URL encoded form with the Shift JIS character set.
The default character set for encoding request bodies is UTF-8.
The default character set for decoding server response entities is defined by the server response’s Content-Type header. If the Content-Type header is missing from the response, then it uses UTF-8.
Reserved HTTP request header characters aren’t escaped and are encoded by the request body’s character set.
The supported encoding set is as defined by the Java JDK. For example, for version 11, supported encoding is documented here (replace the “11” in this URL with your Java SE Platform version number): https://docs.oracle.com/en/java/javase/11/intl/supported-encodings.html - and it’s recommended to use the standard character set encoding name as described by the IANA Charset Registry.