> For the complete documentation index, see [llms.txt](https://partner-docs.covergenius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner-docs.covergenius.com/offers/api/data-formats.md).

# Data Formats

The API adheres to the REST principles and provides developer-friendly, predictable and logically organised resource-oriented structure.

### Dates

Offers API accepts `date` and `date-time` parameters in the format as defined by [RFC 3339, section 5.6](https://tools.ietf.org/html/rfc3339#section-5.6), for example `2018-01-01`, `2018-01-01T17:00:01Z`, `2018-01-01T17:00:00+01:00`, `2018-01-01T17:00:01.04399-04:00`. We encourage partners to keep the original timezone in contrast to sending all dates in UTC. Having original timezone can help Offers API to deal with potential issues with DST changes.

### Country Codes

All country codes provided in API requests must be compliant with [ISO 3166-1 Alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) standard.

### Currency

Currency must be compliant with 3-letter codes as defined by [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217).

### Languages

Language input must be compliant with 2-letter codes as defined by [ISO 639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) standard.\
Variations of base languages use a variant indicator, for example: "en-us" to specify English, United States variant (where applicable).

### Telephone (Mobile Phone) numbers

Phone numbers provided (at offer confirmation stage) should predominantly be of personal mobile/cell type, with the format of `+[country_code]` plus a phone number, e.g., [`+61412345678`](tel:+61412345678)\
\
In some use cases, Offers API will validate the phone number format (to allow sending SMS policy and claim communications to the customer), and return an error if an invalid format is provided.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://partner-docs.covergenius.com/offers/api/data-formats.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.