---
title: "Aqqo"
slug: "aqqo"
description: "Connect Aqqo to Dataddo and sync its data to any dashboard, database, or data warehouse. No coding required."
updated: 2026-07-15T17:29:16Z
published: 2026-07-15T17:29:16Z
canonical: "docs.dataddo.com/aqqo"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dataddo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Aqqo

The Aqqo connector lets you extract data from Aqqo into Dataddo and sync it to any dashboard, database, or data warehouse. Aqqo is a booking platform for court-based sports venues. The connector reads from the Aqqo BI API and covers bookings, courts, locations, users, products, prices, and their audit logs.

Refer to our website for [the list of available metrics and attributes](https://dataddo.com/connector/aqqo) you can extract from Aqqo.

If you have multiple Aqqo accounts and would like to extract the same data from all of them, it's possible through [multi-account extraction](/docs/multi-account-extraction). Contact our Solutions team to enable this feature.

## Authorize Connection to Aqqo

Before you can create a data source, connect Dataddo to your Aqqo tenant.

### Prerequisites

- A Client ID and Client Secret for the Aqqo BI API. Generate them in Aqqo under **Management > Settings > BI API**.
- Your Aqqo tenant ID. It appears in all Aqqo API URLs.

### Create the Authorizer

1. In Dataddo, go to **Authorizers** and click **Authorize New Service**.
2. Select **Aqqo**.
3. Fill in the connection details:

| Field | Details |
| --- | --- |
| Label | A name for this authorizer in Dataddo. |
| Client ID | Your Aqqo BI API Client ID. |
| Client Secret | Your Aqqo BI API Client Secret. |
| Tenant ID | Your Aqqo tenant ID. |

1. Click **Save**.

## Data Coverage

The connector offers the datasets below. The example fields are a representative sample. Each dataset has more fields, and you choose which ones to extract when you create the source.

| Dataset | Description | Example fields | Date range |
| --- | --- | --- | --- |
| Locations | One row per location-court combination, including each venue's address and contact details, its parent company configuration, and the full court settings. | ID, Court ID, Address, Booking Notification Email, City, Company Address (+97 more) | No |
| Courts | Bookable courts with their scheduling configuration, location, and court group context. | ID, Slots Configurable (12/12), Slots Configurable (1/12), Slots Configurable (2/12), Slots Configurable (3/12), Slots Configurable (4/12) (+81 more) | No |
| Companies | Tenant companies with their contact, invoicing configuration, and associated locations, with one row per company-location pair. | ID, Location ID, Address, Attention, City, Country (+52 more) | No |
| Opening Hours | Opening hours configurations with their per-day time slots, with one row per configuration-day combination. | ID, Row ID, Date Added, Date Last Modified, Display Name (de-DE), Display Name (en-US) (+12 more) | No |
| Products | Products available for selection on bookings, with pricing and display configuration. | ID, Bookable From Length, Bookable Till Length, Date Added, Date Last Modified, Default Amount Selected (+52 more) | No |
| Prices | Price records for the tenant, each linked to a price key, VAT code, and court, with an optional validity date range. | ID, Court 12/12 Slots Configurable, Court 1/12 Slots Configurable, Court 2/12 Slots Configurable, Court 3/12 Slots Configurable, Court 4/12 Slots Configurable (+59 more) | No |
| Export Partners | Third-party export integrations available for the tenant, such as accounting or administration systems. | ID, Auth Type, Category, Enabled, Export Type, Level (+2 more) | No |
| Price Keys | Pricing key configurations for the tenant, linked to prices, user groups, and subbookings. | ID, Date Added, Date Last Modified, Default Value, Display Name, Is Deleted (+1 more) | No |
| Usergroups | Usergroup definitions and their assigned price keys. | ID, Date Added, Date Last Modified, Price Key Date Added, Price Key Date Last Modified, Price Key Default Value (+5 more) | No |
| Opening Hour Courts | Opening hours configurations with their per-day time slots and assigned courts, with one row per configuration-day-court combination. | ID, Court ID, Row ID, Slots Configurable (12/12), Slots Configurable (1/12), Slots Configurable (2/12) (+57 more) | No |
| Product Usergroups | Mapping of products to their assigned usergroups, with one row per product-usergroup pair. | ID, Usergroup ID, Bookable From Length, Bookable Till Length, Date Added, Date Last Modified (+56 more) | No |
| Usergroup Courts | Courts accessible to each usergroup, with one row per usergroup-court pair. | ID, Court ID, Court 12/12 Slots Configurable, Court 1/12 Slots Configurable, Court 2/12 Slots Configurable, Court 3/12 Slots Configurable (+50 more) | No |
| Usergroup Court Groups | Court groups assigned to each usergroup, with one row per usergroup-court group pair. | ID, Court Group ID, Court Group Aggregated For Admin Booking Process, Court Group Aggregated For Booking Process, Court Group Aggregated For Price Settings, Court Group Court Tile Enabled (+14 more) | No |
| Usergroup Users | Users belonging to each usergroup, with one row per usergroup-user pair. | ID, User ID, Date Added, Date Last Modified, Price Key Date Added, Price Key Date Last Modified (+59 more) | No |
| Bookings | All bookings for the tenant, including the associated user, user contact, and admin user details. | ID, Admin User Aqqo Information Sent, Admin User Aqqo Notification Read, Admin User Date Last Modified, Admin User Date Last Modified (Legacy), Admin User Display New Admin Layout (+103 more) | No |
| Booking Subbookings | Individual subbookings (court time slots) within bookings, with full booking, user, user contact, and admin user context per row. | Booking ID, Subbooking ID, Admin User Aqqo Information Sent, Admin User Aqqo Notification Read, Admin User Date Last Modified, Admin User Date Last Modified (Legacy) (+145 more) | No |
| Booking Audit Logs | Audit log entries tracking booking status changes, with one row per audit log entry and full booking, user, and admin user context. | Booking ID, Audit Log ID, Admin User Aqqo Information Sent, Admin User Aqqo Notification Read, Admin User Date Last Modified, Admin User Date Last Modified (Legacy) (+110 more) | No |
| Subbookings | Individual court time slots with enriched booking, court, VAT code, price key, and status context. | ID, Activity Display Name, Booking Date Added, Booking Date Last Modified, Booking Display Name, Booking Exclude From Narrowcasting (+118 more) | No |
| Subbooking Audit Logs | Change history for subbookings, with one row per audit log entry and full subbooking and booking context. | Subbooking ID, Audit Log ID, Activity Display Name, Audit Log Admin Roles, Audit Log Date Added, Audit Log New ID (+62 more) | No |
| Users | All user accounts for the tenant, including usergroup membership and contact details. | ID, Access Code Reminder Subscription, Address, Invoice Address, Archived, Attn Invoice (+52 more) | No |
| User Audit Logs | Audit log entries tracking changes to user accounts, with one row per audit event per user. | User ID, Audit Log ID, Access Code Reminder Subscription, Address, Invoice Address, Archived (+58 more) | No |
| Court Groups | Configuration groups used to organise courts for booking, pricing, and display purposes. | ID, Aggregated For Admin Booking Process, Aggregated For Booking Process, Aggregated For Price Settings, Court Tile Enabled, Display Name (+3 more) | No |
| Court Types | Court type definitions that categorise courts and control their terminology within the tenant. | ID, Court Alias, Court Alias Plural, Date Added, Date Last Modified, Display Name (+1 more) | No |
| Vatcodes | VAT rate definitions used for pricing and tax reporting across the tenant. | ID, Country Code ISO2, Date Added, Date Last Modified, Display Name, Display Name Short (+2 more) | No |
| Booking Statuses | Lookup table of all possible booking statuses with their display names and visibility settings. | ID, Display Name, Label, Sticky, Visible | No |
| User Contacts | Contact persons associated with user accounts, used for communication and booking correspondence. | ID, Archived, Date Added, Date Last Modified, Email, First Name (+6 more) | No |
| Opening Hour Rows | Daily opening and closing times per day of the week for each opening hour schedule. | ID, Admin User Closed, Admin User Closing Time, Admin User Opening Time, Date Added, Date Last Modified (+5 more) | No |
| Product Orders | Product orders attached to subbookings, with expanded product, subbooking, and VAT code details. | ID, Book Date, Book End Time, Book Start Time, Custom Product Description, Date Added (+121 more) | No |

## How Data Extraction Works

Aqqo datasets have no date range setting. Every run pulls all data that is currently available in your Aqqo tenant. To keep a full and current copy in your destination, schedule the source and use the replace write mode, or upsert on the `dataddo_hash` column.

## Metadata Columns

You can add two optional Dataddo metadata columns to any Aqqo dataset:

- `dataddo_hash` is a fingerprint of each record's key fields. It works as a natural key and is ideal for upserts.
- `dataddo_extraction_timestamp` is the time the record was extracted. Use it to track slowly changing dimensions.

## How to Create an Aqqo Data Source

1. In Dataddo, go to **Sources** and click **Create Source**.
2. Search for **Aqqo** and select it.
3. Pick the dataset you want to extract.
4. Choose your Aqqo authorizer.
5. Name the data source and select the fields to extract.
6. Click **Test Data** to preview the data.
7. Click **Save**.

## Troubleshooting

### No Data Preview

If **Test Data** shows no preview:

- Check that your Client ID, Client Secret, and Tenant ID are correct.
- Make sure the BI API is enabled for your tenant in Aqqo under **Management > Settings > BI API**.

## Related Articles

Now that you have successfully created a ***data source***, see how you can connect your data to a dashboarding app or a data storage.

**Sending Data to Dashboarding Apps**

- [Simple Data Integration to Dashboards](https://docs.dataddo.com/docs/simple-data-integration-to-dashboards)
- [Data Backfilling to Dashboarding Apps](https://docs.dataddo.com/docs/data-backfilling-to-dashboarding-apps)

**Sending Data to Data Storages**

- [Batch Ingestion to Data Warehouses](https://docs.dataddo.com/docs/ingestion-to-data-warehouses)
- [Data Backfilling to Storages](https://docs.dataddo.com/docs/data-backfilling-to-storages)

**Other Resources**

- [Troubleshooting](https://docs.dataddo.com/docs/troubleshooting)
- [Extraction Logs](https://docs.dataddo.com/docs/extraction-logs)
- [Data Duplication](https://docs.dataddo.com/docs/data-duplication)