Where do I get the API key?

In the iiko web office, under the integration settings of iikoCloud API (iiko Transport). The value is the **apiLogin** of your integration. Renta exchanges it for a short-lived access token on every run, so the key itself is all you store in Renta.

Why does my run fail when I set an old start date?

IikoCloud pipelines refuse a start date more than 90 days in the past. The run stops before any request is sent. Move **Date start** inside the 90-day window, and keep the history that earlier runs already loaded.

Which orders end up in the table?

Every delivery in the selected period, in any state. Renta requests all ten iiko statuses, from **Unconfirmed** through **Delivered**, **Closed**, and **Cancelled**, so cancelled orders arrive as rows too and can be filtered by their status column.

Can one pipeline cover several restaurants?

Yes. **Organisation** is a multi-select, and every organisation you tick lands in the same table. The organizationId column tells the rows apart.

Are orders selected by their creation date or their delivery date?

By delivery date. A run covering a given day returns the orders scheduled for delivery that day, whenever they were created. Add order_created_date to the pipeline if you also need the creation date in the table.

IikoCloud

Renta exports IikoCloud delivery orders to your data warehouse: the order with its status, timing, customer, address, payments, discounts, and the composition of the order.

A pipeline covers the organisations you pick from your iiko account and loads the deliveries of the period you set.

Authentication

Renta authenticates with an IikoCloud API key. The key belongs to an iikoCloud API integration in your iiko web office, where it is labelled apiLogin.

Renta never stores an access token. It exchanges the key for a short-lived token at the start of every run, so revoking the key in iiko cuts Renta off immediately.

Connect IikoCloud as a source

Follow these steps to add IikoCloud as a data source in Renta.

Go to the CatalogStep 1

In the Renta console, open Connections > Catalog in the left sidebar.
Expand the CRM category and click the IikoCloud card. The neighbouring IikoWeb card is a different connector for the iiko web office.

IikoCloud card in the CRM category of the Renta connection catalog

Enter the API keyStep 2

API Key.
The apiLogin value of your iikoCloud API integration.

API Key field on the Add a new IikoCloud connection page

Name the connection and saveStep 3

Fill in Source name, a label used only inside the Renta console, and click Save.

Source name field and the Save button on the IikoCloud connection form

Verify the connectionStep 4

The connection appears in the Sources list with the Active status and is ready for pipelines.

Sources list with the new IikoCloud connection in the Active status

Create a pipeline

A pipeline links the IikoCloud connection to the destination that receives the data.

Create an IikoCloud pipeline

Link your IikoCloud connection to a destination and configure the pipeline.

Select IikoCloud as the sourceStep 1

In the left sidebar, click New pipeline. Keep the ETL tab selected, find IikoCloud under Already connected, and click Next step. The catalog is long, so the search field is the quickest way there.

Select a source step of the pipeline wizard with IikoCloud found through the search field

Select the connectionStep 2

Choose the IikoCloud connection you created and click Next step.

Select your IikoCloud connection step with the API login on the card

Select a destinationStep 3

On the Destination step, pick the warehouse that receives the data and click Next step.

Select a destination step with the connected warehouses

Select the destination connectionStep 4

Choose the destination connection and click Next step.

Pipeline configuration

The last step of the wizard holds every setting in one scrolling form.

Organisation

An iiko account can hold several organisations, and the pipeline reads only the ones you tick here.

The list comes from your iiko account, and each entry shows the organisation name with its identifier below. Ticking several of them loads them all into one table, where the organizationId column separates the rows.

Report type

The report type decides what the pipeline extracts.

Report type	Description
`Delivery orders`	Deliveries of the selected period for the chosen organisations, in every state from Unconfirmed to Cancelled. One row per order, with its status, timing, customer, address, payments, discounts, and items.

Parameters

Tick the fields you want to load. Every field you select becomes a column of the destination table.

The order arrives flattened. Nested parts of the iiko response keep their path in the field name, so order.loyaltyInfo.appliedManualConditions is one field, and its column in the destination replaces the dots with underscores.

Add order_created_date if you want the pipeline to load incrementally. It is the only field Renta can partition the destination table by, and the Overwrite Period setting appears only after you select it.

Integration and table name

Name the pipeline in Renta and the table in your destination.

Integration name and Table name fields in the pipeline settings

Integration name.
The display name of the pipeline in the Renta console.
Table name.
The table in your destination. Keep the generated name or type your own.

Date range

The date range sets which delivery days the pipeline loads.

Date start.
The first delivery day to load.
Date end.
The last one, either a fixed date or a moving boundary such as Today.

Date start cannot be more than 90 days in the past. A run that starts outside this window stops with an error before it sends a single request, and the destination table is left untouched. This applies to a manual Full refresh as well, so a table older than 90 days cannot be rebuilt from scratch.

Overwrite period

The overwrite period defines how far back each scheduled run reloads days it has already loaded. It appears once order_created_date is among the selected parameters.

Orders change after they are created, moving from WaitCooking through OnWay to Delivered or Cancelled. The overwrite window is what brings those changes into the table, so pick a window at least as long as your orders stay open.

Schedule

The schedule decides how often the pipeline runs. Renta reads the times you set here in UTC.

Schedule type	Description
Manual	The pipeline runs only when triggered from the Renta console or through the API.
Daily	The pipeline runs once a day at the specified update time.
Interval	The pipeline runs at specified time intervals.
Cron Expression	The pipeline runs on a schedule defined by a cron expression.

For Daily schedules, set the Update time (the exact time each run starts), then click Create pipeline.

Update time dropdown and the Create pipeline button

Renta also supports API triggers and orchestrators such as Apache Airflow, Dagster, and Prefect. See the scheduling documentation for details.

The pipeline appears in the Pipelines section under the ETL tab, together with the destination table name, run progress, and the number of extracted rows.

Pipelines list with the new IikoCloud integration

Sync strategy

The table below describes how Renta synchronizes the IikoCloud report type.

Strategy	Supported report types	Description
Incremental	`Delivery orders` (with `order_created_date` selected)	The destination table is partitioned by `order_created_date`. Each run deletes the days of the overwrite window and loads them again, so status changes on open orders reach the table.
Full reload	`Delivery orders` (without `order_created_date`)	Without a date column the table cannot be partitioned, so every run replaces its full contents with the current date range.

The 90-day limit and the full reload strategy do not combine well. A pipeline without order_created_date rewrites the table on every run and can only ever reach back 90 days, so history older than that is lost on the next run. Select order_created_date whenever you intend to keep more than a quarter of orders.

Frequently asked questions

Ready to get started?

Build your data pipeline today or get a personalized demo. Start free!

Need help?

Get expert support to ensure your project succeeds. We're here to help!

Feature requests?

Help shape our product! Share your ideas for new features and integrations.