# API reference

Requests and responses for sending invoices, connecting companies and retrieving purchase invoices, and the GETS format the invoices use.

## Base URL

```
https://prod.gets.complyance.io
```

Use the environment selector documented for each operation. The hostname alone does not select production data.

## APIs

- [Unify](https://docs.complyance.io/api-reference/unify/): Send invoices in GETS and follow each document's status (`Authorization: Bearer`)
- [GETS schema](https://docs.complyance.io/api-reference/gets/): The invoice format Unify accepts: fields, document types, modifiers and country extensions
- [Connect](https://docs.complyance.io/api-reference/connect/): Onboard UAE companies, add branches and read document counts (`X-API-Key`)
- [Purchases](https://docs.complyance.io/api-reference/purchases/): List received purchase invoices and retrieve their full data (`Authorization: Bearer`)

Requests and responses use JSON unless an endpoint explicitly returns a file. Keep API keys on your server.

Start with [authentication and environments](https://docs.complyance.io/api-reference/authentication/). For a complete submission walkthrough, follow [your first UAE invoice](https://docs.complyance.io/partner-platform/isv/first-uae-invoice/connect/).

Source: https://docs.complyance.io/api-reference/