# Erli

Erli integration with Ritevo: connecting the account with an API key, fetching orders, pickup points, buyer messages over email, reconnecting.

The Erli integration brings orders from your seller account into Ritevo. You connect it with an API key from the Erli seller panel. Erli delivers buyer messages by email - you handle them in Ritevo through an email integration.

> **Required integration:** You need an active Erli seller account and an API key generated in its panel.

One Erli account is connected once; if you sell from several accounts, add each one as a separate integration.

The same Erli account can be connected only once. When you connect it again, Ritevo refreshes the existing integration and turns it back on, even if it was deleted.

Uniqueness: the integration is unique within the company by `externalId` and the type `ERLI`. Creating it again refreshes the existing integration instead of adding a new one: it sets `authError=false` right away, and `active=true` if the integration was inactive. You can also send new credentials with `PATCH /integrations/marketplaces/erli/{id}/token` - in any state of the integration, also when `authError=false` and `active=true`; it sets `authError=false` and `active=true`.

## How to generate the API key

You create the API key in the Erli seller panel. Copy it in full - you will paste it into Ritevo when adding the integration.

1. Sign in to the Erli seller panel.
2. In the top right corner open **Moje ERLI** and choose **Ustawienia sklepu** (shop settings).
3. In the left menu choose **Metoda integracji** (integration method), then **Własna integracja po API** (own API integration).
4. In the **Opis klucza** (key description) field enter any name, for example "Ritevo", and click **Wygeneruj nowy klucz** (generate new key).

## Connecting the account

Start in Ritevo:

1. Go to **Integrations** in the left panel and click **Add integration** in the top right corner.
2. In the **Marketplace** section pick the **Erli** tile.
3. In the **API Token** field paste the API key from your Erli seller panel.
4. Click **Add integration**. Ritevo checks the key with Erli right away: if it is valid, the integration is added and its settings open. If not - you will see the error returned by Erli and nothing is saved.

![The integrations list in Ritevo with the Add integration button in the top right corner framed](https://ritevo.com/docs/integrations/en-integrations-list.webp)

![The Add integration screen with the Erli tile framed in the Marketplace section](https://ritevo.com/docs/integrations/erli/en-catalogue.webp)

![The Erli add-integration screen with the API Token field and the Add integration button](https://ritevo.com/docs/integrations/erli/en-add.webp)

## Integration settings

After connecting, the integration is **Active**, but order and message fetching are **off** - you turn them on yourself, separately:

- **Account name** - the name of your seller account, which Ritevo takes from Erli. It cannot be changed.
- **Fetch orders** - once on, Ritevo checks for new and changed orders about every 10 minutes. The rules shared by all channels: [Fetching orders](https://ritevo.com/en/docs/orders/fetching-orders).
- **Fetch messages** - instead of a switch there is a note that Erli messages are handled through an email integration, and an **Add integration** button that leads to adding one.

![Erli integration details: the account name, the Fetch orders switch, the messages card pointing to the email integration and the Update credentials button](https://ritevo.com/docs/integrations/erli/en-details.webp)

> **Good to know:** You can replace the key at any time with the same **Update credentials** button, not only after an error.

## What this integration gives you

- **Orders** - new and updated Erli orders land in the orders table, with the buyer's details, invoice details, delivery (including the pickup point) and line items with images.
- **Messages** - through an email integration, see below.

## Orders from Erli

Ritevo fetches the whole Erli order: the buyer, payment, delivery together with the pickup point, line items with prices and product images.

- **Statuses and payments** - Erli statuses and payment methods are translated to Ritevo statuses in one fixed way; marketplaces have no mappings of their own, unlike online stores. A cash-on-delivery order arrives as **Awaiting payment** with the **Cash on delivery** method.
- **Returns** - an order the buyer has returned is still shown by Erli as purchased; in Ritevo it stays **Confirmed**.
- **Additional services** - not supported. This integration does not pass on services such as gift wrapping or carry-in. If you want to sell them, list them as a separate product or offer - they then show in the order as a regular line item. More about [additional services](https://ritevo.com/en/docs/orders/fetching-orders#additional-services).
- **Invoice** - if Erli provides the buyer's tax id or its equivalent, the order gets the **Customer asks for an invoice** flag with the company details and the number filled in.

> **Good to know:** An order with the **Confirmed** status is taken over by Ritevo - later changes on the sales channel's side are skipped. More in [Fetching orders](https://ritevo.com/en/docs/orders/fetching-orders#who-manages).

## Buyer messages from Erli

Erli has no inbox of its own - buyers write to you **by email** to the address set in your Erli account. To see and answer those messages in Ritevo, add an [email integration](https://ritevo.com/en/docs/messages/fetching-messages) for that mailbox. The messages then appear in Ritevo like ordinary emails; they are not linked to the Erli integration or its orders.

## Reconnection required

This state appears when the API key stopped working - it was revoked in the Erli panel or lost its permissions. Until you provide a new key, Ritevo neither fetches nor sends any data on that account.

1. Generate a new API key in your Erli seller panel.
2. On the integration page in Ritevo click **Update credentials**, paste the new key and confirm. Ritevo checks it with Erli just like when adding - a wrong key returns an error, a valid one refreshes the connection. The fetching settings and the history stay unchanged.

> **Good to know:** Reconnecting clears the **Reconnection required** state straight away and turns the integration on - also when it was deleted earlier. You do not need to restore it separately.

In the API, reconnecting sets `authError=false` and `active=true` on the integration, also when it was deleted (`active=false`). Which endpoint does it for a given integration is described in the uniqueness note at the top of the page.

## Deleting the integration

**Delete integration** turns the integration off in Ritevo: it stops fetching and sending data, but what it fetched earlier stays. **Restore integration** turns it back on.

## What the integration does not do

- It does not manage listings: it does not list, change prices or stock in Erli.
- It does not fetch messages or disputes - Erli does not expose them through its API.

## The integration through the API

This integration's endpoints are under `/integrations/marketplaces/erli`, and the ones shared by the whole type (list, get one, fetching switches, delete, restore) under `/integrations/marketplaces`. The current paths, fields, types and response codes are always in Swagger: https://api.ritevo.com/api/v1/api-docs.


---

All help in one file: https://ritevo.com/llms-full.txt. Help map with links to every page: https://ritevo.com/llms.txt.