🚀 Partner Example App

A partner application example that performs Aircall's OAuth flow and subscribes to webhook events on the Public API.

Want to build an integration with Aircall? Check out our API documentation

What is this?

This app is an example of how you can easily connect to Aircall's ecosystem. It:

• implements Aircall's OAuth flow
• creates a webhook on Aircall so it is notified on specific events

Endpoints

GET /oauth/install

See code

This endpoint is the entry-point of the install flow of the application. It is called when a user clicks on "Install" in Aircall's dashboard. It redirects to the Aircall consent page so the user can authorize the application.

You can implement custom logic at this step, however you must redirect to Aircall's consent page at the end of your execution.

GET /oauth/callback

See code

This endpoint is called once the user has authorized the application. An authorization_code is given in the code GET param, which can be used to create an access token in order to interact with Aircall's Public API. The code param is fetched from the URL, then the Oauth::CreateAccessToken service is called to create the access token on Aircall's Public API. Once this is done, the Webhooks::Create service is used to create a webhook on Aircall's Public API.

POST /webhooks

See code

This endpoint is called when a subscribed event happens on Aircall. In this example, the call.created event is subscribed to, so POST /webhooks will be called everytime an inbound or outbound call is created.

Running locally

Pre-requesites: a running Docker engine.

Environment variables

You need to have a .env file at the root of the folder with all variables described in .env.example Fill your OAuth client id and secret with the values provided by Aircall. If you don't have those, fill in this form and we'll be in touch.

In order to launch the tests, you will need a .env.test file at the root of the folder with all variables described in .env.example. You can use any value for the env variables in the test environment.

Running the app

Once your environment variables are setup, you can use:

• docker-compose up --build to launch the server. Whenever a file is changed, the server is restarted, tests are re-runned and doc is generated.
• docker-compose down to stop all containers created by up

Once the app is running, head to localhost:3000/oauth/install to launch the OAuth flow. You can visit localhost:3011 to see the YARD documentation of the project.