Overview
Getting Started
Aircall supports two ways to authenticate with the REST API: Basic Authentication and OAuth.
Use Basic Authentication when you are connecting your own internal tools or private integration to Aircall. Use OAuth when your app needs to access Aircall data on behalf of other users or customers.
| Use case | Basic Authentication | OAuth |
|---|---|---|
| Connect your own system and tools to Aircall | ✅ | ❌ |
| Build an integration for multiple Aircall users outside your organization | ❌ | ✅ |
This guide explains the two methods in more detail and helps you choose the right authentication method before you start building.
Basic Auth
Basic Authentication uses an API ID and token that you generate directly from your Aircall Dashboard.
To connect a tool or service, you copy these credentials and paste them into the platform you want to integrate with — no authorization flow required. Use it when you want to connect quickly without setting up an authorization flow.
When to use Basic Auth
- You're connecting your own system or tool to Aircall
- You don't need to access data on behalf of other users
- You're building a private integration and are not an approved tech partner
For full technical details, see the REST API reference > Basic Auth
OAuth
OAuth lets your application access Aircall data on behalf of a user after they grant permission. It's more complex to implement than Basic Authentication, but it's the standard approach for integrations that serve multiple customers.
When to use OAuth
- You're building an integration for multiple Aircall users
- Users need to authorize access to their own Aircall accounts
- You’re building a public integration and are an approved tech partner
For full technical details, see the REST API reference > OAuth
Updated 3 days ago
What’s Next
Choose one of the guides below to continue setting up authentication