Plivo Android SDK

    The Plivo Android SDK lets you create applications capable of making and receiving calls in your Android app. This SDK support both IPv4 and IPv6 networks, which means you can make and receive calls when your device is connected to a network that uses either or both versions of the protocol. The SDK supports Android versions 6 and above.

    Prerequisites

    Before you start coding your app:

    1. Register for a Plivo account. You need a Plivo account to create endpoints and Plivo High-Level Objects (PHLO).

    2. Create a Plivo endpoint to facilitate making and receiving calls from the Android client. For more information about endpoints and their usage, see the endpoint concepts documentation. You can automate the creation of endpoints using our REST API. Refer to our Endpoint API Reference Guide for details.

    3. Download and install the latest version of Android Studio.

    4. Create a PHLO and link it with your endpoint.

    Getting started with the Plivo Android SDK

    To create a VoIP-enabled Android app:

    1. Download the aar and add to your app/libs.

      Alternatively, you can include this script into your app/build.gradle file:

       allprojects {
         repositories {
           mavenCentral()
         }
       }
      
       dependencies {
         implementation 'com.plivo.endpoint:endpoint:2.0.19'
       }
      

      New Android artifact location: https://search.maven.org/artifact/com.plivo.endpoint/endpoint/2.0.19/aar

    2. Use our Plivo Voice Quickstart for Android example app as a starting point to create your app. Use our Best Practices Guide to build the Android app efficiently.

    3. Refer to Android SDK Reference documentation for more details on creating applications capable of making and receiving calls in your app.

    4. To set up incoming calls with push notifications, see Setting Up Push Notifications.

    5. To manage Android push credentials on the console, see Manage Push Credentials.

    6. To debug the basic call related issues, see our Client SDK Troubleshooting Guide.