Skip to main content

Authorization

Follow this guide to create a new AppsFlyer credential that will allow Nexla to authenticate to and exchange data with your AppsFlyer account.
apps_flyer_api_auth.png

AppsFlyer

Prerequisites​

The AppsFlyer connector authenticates to the AppsFlyer REST APIs using an API V2 token (a JWT) issued from the AppsFlyer Security Center. The token is sent on every request as an Authorization: Bearer <token> header. Generate the token in AppsFlyer before creating the credential in Nexla.

Generate an AppsFlyer API V2 Token​

The API V2 token is issued from the Security Center in your AppsFlyer dashboard. Only account admins can create or rotate API tokens.

  1. Sign in to your AppsFlyer account at hq1.appsflyer.com.

  2. Open the account menu by clicking your email address in the top-right corner of the dashboard, and select Security Center from the dropdown.

  3. In the Security Center, locate the AppsFlyer API tokens section and click Manage your AppsFlyer API tokens. The list of currently active tokens is displayed.

  4. Click Create Token to open the token creation dialog.

  5. Select API as the token type, and click Create. AppsFlyer immediately issues a new API V2 token (JWT) and displays it once on screen.

  6. Copy the token and store it in a secure secret manager. AppsFlyer does not display the token again after the dialog is closed, and the token cannot be retrieved later.

    By default, every new AppsFlyer account is provisioned with one API V2 token. Admins can create a maximum of two API tokens per token type. API V2 tokens are active immediately after creation and do not require an additional activation step.

For complete information about creating, rotating, and revoking AppsFlyer API tokens, see the Managing AppsFlyer tokens help center article.

Important

The API V2 token grants full read and write access to your AppsFlyer account data. Treat it like a password — store it in a secret manager, never commit it to source control, and rotate it immediately if you suspect it has been exposed. AppsFlyer recommends rotating API tokens at least every 180 days.

Create an AppsFlyer Credential​

  • To create a new AppsFlyer credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

Credential Name & Description​

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

    Resource descriptions are recommended but are not required. They should be used to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

Authentication Method​

  1. Enter the AppsFlyer API V2 token generated above in the API V2 Token field. Nexla will use this value to send Authorization: Bearer <token> on every API call to AppsFlyer.

    The API V2 Token field is masked and stored encrypted by Nexla. To rotate the token in the future, generate a new token in AppsFlyer's Security Center and update this field on the credential — no other configuration changes are required.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential. Nexla validates the token by issuing a GET https://hq1.appsflyer.com/api/mng/apps call before storing the credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.