Aircall

Aircall is a cloud-based phone system designed for modern teams, providing voice communication, call management, and analytics tools to enhance customer support and sales operations with seamless integration capabilities.

Power end-to-end data operations for your Aircall API with Nexla. Our bi-directional Aircall connector is purpose-built for Aircall, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Aircall or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Aircall workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an Aircall credential in Nexla, you need to obtain your API ID and API token from your Aircall Company Settings. These credentials authenticate Nexla with the Aircall Public API and should be kept secure.

1. Sign in to your Aircall account.

2. Navigate to Company Settings in your Aircall account to access the company settings page.

3. Locate the API section in the Company Settings menu. This section contains your API credentials for accessing the Aircall Public API.

4. Copy your API ID. This is a unique identifier that authenticates API requests and provides access to your Aircall account. The API ID is used as the username for basic authentication.

5. Copy your API Token. This is a secret token that authenticates API requests and provides access to your Aircall account data. The API token is used as the password for basic authentication.

   Your API ID and API Token are required for all Aircall API operations. Keep these credentials secure and do not share them publicly or commit them to version control systems. For detailed information about Aircall API authentication, see the Aircall API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API ID	Yes	No	Your Aircall API ID. You can find it in the Company Settings section.
API Token	Yes	Yes	Your Aircall API Token. You can find it in the Company Settings section.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Aircall

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Aircall API ID in the API ID field. This should be the API ID obtained from your Aircall Company Settings. The API ID is used as the username for basic authentication.

4. Enter your Aircall API Token in the API Token field. This token authenticates Nexla with the Aircall Public API and should match the API token obtained from your Aircall Company Settings. The API token is used as the password for basic authentication.

   The API ID and API Token provide full access to your Aircall account data through the API. Keep these credentials secure and do not share them publicly or commit them to version control systems. Aircall uses basic authentication with the API ID and token, which allows Nexla to make authenticated requests to your account.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Aircall connector tile, then select the credential that will be used to connect to the Aircall instance, and click Next; or, create a new Aircall credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Aircall endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get Records of Type

This endpoint retrieves a list of all records of a specified resource type from your Aircall account. Use this endpoint when you need to access users, contacts, or other resource types for analysis, reporting, or integration with other systems.

• Select the resource type you want to retrieve from the Resource Type dropdown menu. Available options include Users and Contacts. You can also add custom resource types if needed.
• The endpoint uses page-based pagination, automatically fetching additional pages as needed. By default, the endpoint retrieves up to 50 records per page, starting from page 1.
• The endpoint will return all records of the selected resource type, organized into pages for efficient data retrieval.

This endpoint supports pagination through page and per_page parameters. Nexla automatically handles pagination to retrieve all available records. For detailed information about available resource types and API endpoints, see the Aircall API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Aircall data sources can also be manually configured to ingest data from any valid Aircall API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Aircall API endpoints typically follow the pattern https://api.aircall.io/v1/{resource_type}, where {resource_type} is the type of resource you want to access. For a complete list of available Aircall API endpoints, see the Aircall API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Aircall data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Aircall destination, and select the Send to Destination option from the menu. Select the Aircall connector from the list of available destination connectors, then select the credential that will be used to connect to the Aircall organization, and click Next; or, create a new Aircall credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Aircall endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Records

This endpoint creates new records of a specified resource type in your Aircall account. Use this endpoint when you need to create users, contacts, or other resource types from your Nexset data. Each record should include all properties needed by that resource type.

• Select the resource type you want to create from the Resource Type dropdown menu. Available options include Users and Contacts. You can also add custom resource types if needed.
• The endpoint will send the Nexset data as JSON in the request body to create records. Ensure your Nexset contains all required fields for the selected resource type. See the API documentation for details about required properties for each resource type.
• Each record in the Nexset will be sent as a separate API request to create a new record in your Aircall account.

The request body must contain valid JSON with all required fields for the selected resource type. For detailed information about required fields and data formats for each resource type, see the Aircall API documentation.

Manual configuration

Aircall destinations can also be manually configured to send data to any valid Aircall API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Aircall API endpoints typically expect JSON format for request bodies. Endpoints follow the pattern https://api.aircall.io/v1/{resource_type}, where {resource_type} is the type of resource you want to create or update. For update/upsert operations, include the ID of the object to be updated at the end of the URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Aircall endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Aircall endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.