Objective

This article helps you store a mobile push credential on your account so Twilio can deliver push notifications to your iOS or Android application.

Product

Programmable Voice

Environment

Twilio Console

User Account Permission/Role(s) Required

Your user must have permission to update Voice settings on the account.

Procedure

1. In the Twilio Console, select Communications in the left sidebar.
2. Select Voice, then Settings.
3. Select the Voice credentials tab, then the Mobile Push Credentials sub-tab.
4. Select Create Mobile Push Credential.
5. In Create new Mobile Push Credential, enter a Friendly Name.
6. Choose a Type:
   • APNs - Apple Push Notification service
   • FCM - Firebase Cloud Messaging
   • GCM - Google Cloud Messaging
7. Complete the fields for the type you chose:
8. For APNs, enter the Certificate and Private key, and select Use this credential for sending to a sandbox APNs. if this credential is for the sandbox environment.
9. For FCM, enter the FCM API Key.
10. For GCM, enter the GCM API Key.
11. Select Create.
12. A Mobile Push credential created confirmation appears and the new credential appears in the table with its identifier, creation date, and type.

Additional Information

• Validation rules and messages:
• The friendly name is required, must be at least 3 characters, and can be up to 64 characters.
• The type is required.
• An APNs certificate and private key are both required, and the private key must be at least 20 characters. The private key help text asks for the URL encoded representation of the private key.
• An FCM or GCM API key is required and must be at least 16 characters.
• Leave the sandbox checkbox unchecked to send to production, as its help text notes.
• Select Cancel to close the panel without creating a credential.
• If your account already has several pages of credentials, the new entry may appear on a later page — use Go to next page to find it.

This content was generated by AI and reviewed, edited, and verified by a human.