> ## Documentation Index
> Fetch the complete documentation index at: https://www.latitude.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Encoding

> Character encoding and content types

Data is encoded as defined by JSON in [RFC4627](http://www.ietf.org/rfc/rfc4627.txt). The default encoding for APIs is UTF-8. Certain characters, such as Emoji may be handled as surrogate unicode pairs (see section '2.5. Strings' of [RFC4627](http://www.ietf.org/rfc/rfc4627.txt)).

Some query parameters may need to be [url encoded](https://en.wikipedia.org/wiki/Percent-encoding) when sending - for example, the `email` parameter value used to query users should be encoded.

<Warning>
  **HTML Encoding**

  It should be noted that the following identifiers are encoded to protect from potential cross-site scripting attacks: `name`, `user_id`, `company_id` and `email`. As a result you may see these identifiers in their encoded format when you retrieve them via the API.

  Note that the characters we encode are double quote, single quote, ampersand, less than and greater than symbols i.e " ' & \< >
</Warning>

```text HTML Encoding example theme={null}
Let's say you have a company name like "BL&T's".
Then when you retrieve it from the API it will look like this:
"BL&amp;T&#39;s"
```