> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/api-documentation/standard-practices/general-info.md).

# General Info

The Emporix API follows standardized practices for data consistency, using ISO and IETF formats for countries, currencies, dates/times, and languages across its services.

## Standard practices in the Emporix API

Here you can find descriptions of practices, concepts, and data formats that are commonly used across the Emporix API services.

### Data standardization

To ensure consistency between the Emporix API services, some data types use standardized formats:

| Data type           | Description                                                                                                                                                                  |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Countries**       | Countries are indicated through two-letter codes compliant with the [ISO 3166-1 alpha-2 standard](https://www.iso.org/obp/ui/#iso:pub:PUB500001:en).                         |
| **Currencies**      | Currencies are indicated through three-letter codes compliant with the [ISO 4217 standard](https://www.iso.org/iso-4217-currency-codes.html).                                |
| **Dates and times** | All dates and times are stored as instantaneous moments in the UTC timezone, compliant with the [ISO 8601 standard](https://www.iso.org/iso-8601-date-and-time-format.html). |
| **Languages**       | Languages (including regional variants) are indicated through codes compliant with the [IETF BCP-47 standard](https://en.wikipedia.org/wiki/IETF_language_tag).              |

Check the below for specific practices:

* [Mixins](/api-documentation/standard-practices/mixins.md)
* [Translations](/api-documentation/standard-practices/translations.md)
* [Query Parameter](/api-documentation/standard-practices/q-param.md)
* [Pagination](/api-documentation/standard-practices/pagination.md)
* [Upsert](/api-documentation/standard-practices/upsert.md)
* [Custom ID](/api-documentation/standard-practices/custom-id.md)
* [Bulk Request Limits](/api-documentation/standard-practices/bulk-request-limits.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.emporix.io/api-documentation/standard-practices/general-info.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.