Where do I get the API key and the user hash key?

Both come from the Altegio Marketplace. Register there as a developer and the API key shows up in the **Account settings** section. The user hash key appears in the **User token** field of the same application once you enter the ID of an Altegio user and save.

Which locations show up in the Companies dropdown?

The ones the Altegio user behind the user hash key can reach. If a location is missing, grant that user access to it in Altegio, then reopen the pipeline settings.

How do I tell which location a row came from?

By the Company ID column. Every report type has one, so a pipeline covering several locations stays readable in a single table.

Can one pipeline export several report types?

No. A pipeline carries one report type, so create a separate pipeline for each Altegio object you want in the warehouse.

How far back does Staff salary go?

To 1 January 2024. The window ends on the day the run starts and is not configurable.

Does the pipeline load only the records changed since the previous run?

No. Every run reads the selected report type in full and replaces the destination table.

Altegio

Renta exports seven kinds of Altegio data to your data warehouse: finance transactions, client appointments with their services and documents, day by day payroll for every staff member, the service catalog with its categories, the staff roster, and the profile of each location.

A salon chain runs on several locations, and Altegio calls them companies. One pipeline covers as many of them as you need, and the rows land in one table where the Company ID column tells them apart.

You pick the fields of each report type yourself. Every report type reloads in full on each run, so the destination table repeats the Altegio account as it was when the run started.

Authentication

Renta connects to Altegio with two values issued by its Marketplace: the API key, which identifies the application, and the User hash key, which identifies the user the application acts on behalf of.

API key.
Register in the Altegio Marketplace as a developer. Altegio issues the key itself, and you find it in the Account settings section of the Marketplace.
User hash key.
Open the API access settings of the same application and fill in the User ID field. To find that ID, go to Settings > List of users in Altegio and open the user. The ID is the second number in the address bar. Save the settings, and the value shows up in the User token field.

The user behind the hash key determines what the pipeline can reach. Only the locations that user has access to appear in the Companies dropdown, and only the data their permissions allow arrives in the warehouse.

Grant the user access to every location you plan to export before you connect the source. A location added in Altegio later shows up in Companies only after the user gets access to it.

Connect Altegio source

Follow these steps to add Altegio as a source in Renta using the API key and the user hash key.

Go to the CatalogStep 1

Navigate to the Connections > Catalog section in the left sidebar.
Open the CRM category and click the Altegio card.

Altegio card in the CRM category of the Renta connection catalog

Paste the keysStep 2

In the API key field, paste the key from the Account settings section of the Altegio Marketplace.
In the User hash key field, paste the value from the User token field of your Marketplace application.

Add a new Altegio connection page with the API key and User hash key fields

Name the connection and saveStep 3

In the Source name field, specify a name for this data source. It is used exclusively in the Renta interface.
Click Save.

Renta asks Altegio for the list of locations before saving, so a mistyped key or a user without access fails right on this step.

Altegio connection setup with the source name field filled in and the Save button

Source createdStep 4

The new source appears in the Sources list with the Active status. You can now use it in pipelines.

Sources list with the new Altegio source in the Active status

Create a pipeline

Once the source is connected, create a pipeline to sync your Altegio data into your destination.

Create an Altegio pipeline

Link your Altegio source to a destination and configure the pipeline.

Select Altegio as the sourceStep 1

In the left sidebar, click New pipeline. On the Source step, select Altegio under Already connected and click Next step.

Select a source step with Altegio under Already connected

Select your Altegio connectionStep 2

Choose the Altegio connection you created earlier and click Next step. The card shows the name of the connection and the date it was added.

Select your Altegio connection step with the connection card and its creation date

Select a destinationStep 3

On the Destination step, select your destination (for example, Google BigQuery) and click Next step.

Select a destination step with Google BigQuery under Already connected

Select the destination connectionStep 4

Choose the destination connection you want to load data into and click Next step. The card shows the dataset and project the data will land in.

Select your Google BigQuery connection step with the dataset and project identifiers on the card

Pipeline configuration

On the final step, choose the locations and the report, pick its fields, and set the schedule.

Companies

Select the Altegio locations the pipeline covers. The dropdown is filled from your Altegio account, and you can tick as many locations as you need.

Everything you tick lands in one destination table. The Company ID column marks which location a row belongs to, and it is available in all seven report types, so add it whenever a pipeline covers more than one location.

The Selected Companies list below the dropdown shows your current choice and lets you drop a location from it.

Report type

Select which Altegio object the pipeline exports. One pipeline loads one report type.

Report type	Description
Appointments report	Appointment records with the visit date and time, attendance and confirmation status, the number of clients, the comment left on the record, the user who created it, the booking form it came from, and the deleted flag. Client, staff, services, documents, and goods transactions arrive as nested structures.
Company metadata	The profile of the location: title, category, logo, phone, operating schedule, address, city, country, timezone, currency abbreviation, and whether the license is paid.
Service categories metadata	The service categories of the location with the category and service identifiers, the booking title, the minimum and maximum price, the staff who can perform the service, the gender restriction, and the sort weight.
Service metadata	The service catalog with duration, technical break, capacity, price range and discount, prepayment and autopayment settings, tax variant and VAT, online booking availability, the category the service belongs to, the booking and print titles, and the active flag.
Staff metadata	The staff roster with name, specialization, position, rating, email and phone, avatars, online booking settings, the linked user account, and the dismissal date and reason for those who left.
Staff salary	Day by day payroll for every staff member: salary, the count and sum of services, the count of group services, the count and sum of goods sales, total sum, working days, and working hours.
Transactions	Finance transactions of the location: amount, the account the money went through and whether it was cash, the client, the linked service record, the visit and document identifiers, the expense category and type, the sold item, a comment, and the date of the last change.

Staff salary covers calculations from 1 January 2024 up to the day the run starts. The pipeline has no date range setting, so the depth of payroll history is fixed and earlier periods stay out of the warehouse.

Parameters

Select the Altegio fields to include in the destination table.

Each entry on the Parameters tab shows the field name and, below it, the column name it takes in the destination table. Use the search field to find a parameter by name, or click Select All. The Selected tab shows everything you picked, and the Selected Parameters list below the picker lets you remove a parameter.

The set of available fields depends on the report type, and no field is picked for you.

In Appointments report, five fields hold whole objects rather than single values, and Renta writes them as nested structures instead of splitting a record across rows.

Field	What it holds
Client [Object]	The client of the appointment: name, phone, email, discount, loyalty card, and the counts of successful and failed visits.
Documents [Object]	The documents attached to the visit, with their number, type, category, storage, and creation date.
Goods transactions [Object]	The goods sold during the visit, with article, barcode, price, discount, and the storage they left.
Services [Object]	The services rendered, with title, amount, cost, cost per unit, discount, and the manual cost flag.
Staff [Object]	The staff member who took the appointment, with specialization, rating, and votes count.

Transactions carries the moment of payment twice. Transaction datetime keeps the full timestamp, and Transaction date holds the same moment as a calendar day, which is what you group by for daily revenue.

Table name

Name the pipeline and the destination table.

Integration name.
The name of the pipeline. It is used exclusively in the Renta interface.
Table name.
The destination table name. You can keep the auto-generated name or enter your own.

Schedule

Choose how often the pipeline runs.

Schedule type	Description
Manual	The pipeline runs only when triggered manually through the interface or via 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 selection and the Create pipeline button

A Staff salary run rebuilds a multi-year window for every staff member of every ticked location, so it takes noticeably longer than the other report types. Give it a schedule of its own rather than stacking it on the same hour as the rest.

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

The new pipeline appears in the Pipelines section under the ETL tab, where you can track its runs, progress, and the destination table name.

Pipelines list with the new Altegio integration in the Completed status

Sync strategy

Renta synchronizes every Altegio report type the same way.

Strategy	Supported report types	Description
Full reload	Transactions, Company metadata, Appointments report, Service categories metadata, Service metadata, Staff salary, Staff metadata	Every run reads the selected report type in full for every ticked location and replaces the contents of the destination table. Nothing narrows a run down to the records changed since the previous one, and no record is matched and updated in place. The table repeats the Altegio account at the time of the run, so a record that Altegio stops returning, such as a deleted appointment, leaves the table on the next run.

Because every run reads the report type in full, the pipeline has no date range or overwrite period settings. Destination tables stay unpartitioned, so a query over a long transaction history scans the whole table.

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.