AppsFlyer API

Name: AppsFlyer API
Brand: AppsFlyer API
Availability: InStock

✓ Official Vendor SpecAnalyticsProduct Analyticsbearer, apiKey10 EndpointsREST

For Agents

Pull AppsFlyer mobile attribution data - installs, in-app events, uninstalls, and aggregate marketing reports - and ingest server-to-server events.

Install Jentic One Beta

Connect the AppsFlyer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AppsFlyer API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AppsFlyer API.

List the apps registered in an AppsFlyer account via /apps/v1.0/list

Export raw install records via /raw-data/export/app/{app_id}/installs/v5

Export raw in-app event records via /raw-data/export/app/{app_id}/in-app-events/v5

GET STARTED

Start building with AppsFlyer API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AppsFlyer API for, with concrete tasks.

★ Attribution data into the warehouse

Schedule an ETL job that calls the raw-data export endpoints (installs, in-app events, uninstalls) on a regular cadence, drops the resulting CSVs into S3, and loads them into Snowflake or BigQuery. From there, marketing analysts join attribution against revenue, cohort, and CRM data without paying per query in the AppsFlyer UI. This is the standard pattern for any growth team that has its own warehouse.

Call /raw-data/export/app/{app_id}/installs/v5 with from and to date params for the last 24 hours and write the response CSV to s3://attribution-raw/installs/.

Server-to-server event ingestion

Send post-install events from the backend to AppsFlyer through POST /inappevent/{app_id} so attribution and remarketing signals stay accurate even when conversion happens server-side (subscription renewal, customer service refund, B2B activation). This avoids relying on the mobile SDK alone and ensures revenue events are credited to the originating campaign.

POST /inappevent/{app_id} with eventName=af_purchase, eventValue, customerUserId, and the original installation's appsflyer_id.

Aggregate reporting in dashboards

Pull AppsFlyer aggregate reports (partner_by_date, geo_by_date) and render them in a BI dashboard without buying additional AppsFlyer reporting seats. The aggregate endpoints return the same numbers as the AppsFlyer UI tables and are well suited to a Looker or Metabase dashboard refreshed on a daily cadence. Reduces seat cost and gives analysts the data alongside other sources.

Call /aggregate/v2.0/partners_by_date/app/{app_id} with from=last_30d, to=today and store the rows in a Snowflake table for the dashboard.

Agent integration via Jentic

Give a growth-marketing agent a small set of attribution-data tools through Jentic. The agent can answer 'how many installs did Facebook drive last week?' by loading /aggregate/v2.0/partners_by_date and 'send a renewal event to AppsFlyer' by loading /inappevent/{app_id}, with both Bearer and API-key credentials kept in your Jentic One instance.

Search Jentic for 'AppsFlyer installs by partner', load /aggregate/v2.0/partners_by_date/app/{app_id}, and execute it with the requested app and date range.

Key Endpoints

10 endpoints — the appsflyer api exposes the company's mobile attribution and marketing analytics platform, covering install, in-app event, uninstall, and aggregate reports along with server-to-server event ingestion and basic user management.

METHOD

PATH

DESCRIPTION

GET

/apps/v1.0/list

List apps registered in the AppsFlyer account

GET

/raw-data/export/app/{app_id}/installs/v5

Export raw install records for an app

GET

/raw-data/export/app/{app_id}/in-app-events/v5

Export raw in-app event records

GET

/raw-data/export/app/{app_id}/uninstalls/v5

Export raw uninstall records

POST

/inappevent/{app_id}

Ingest a server-to-server in-app event

GET

/aggregate/v2.0/partners_by_date/app/{app_id}

Partner-by-date aggregate report

GET

/aggregate/v2.0/geo_by_date/app/{app_id}

Geo-by-date aggregate report

GET

/v1.0/users

Manage AppsFlyer users

GET

/apps/v1.0/list

List apps registered in the AppsFlyer account

GET

/raw-data/export/app/{app_id}/installs/v5

Export raw install records for an app

GET

/raw-data/export/app/{app_id}/in-app-events/v5

Export raw in-app event records

GET

/raw-data/export/app/{app_id}/uninstalls/v5

Export raw uninstall records

POST

/inappevent/{app_id}

Ingest a server-to-server in-app event

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your AppsFlyer bearer token or API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'export installs raw data', and Jentic returns the matching AppsFlyer operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using AppsFlyer API through Jentic.

What authentication does the AppsFlyer API use?

Authentication is split between two schemes. Raw data and aggregate report endpoints use a Bearer token issued from the AppsFlyer dashboard, while server-to-server event ingestion (/inappevent/{app_id}) and user management use an API key in the Authorization header. Through Jentic both credentials sit in your Jentic One instance and the right one is injected per operation.

Can I export raw install and in-app event data with the AppsFlyer API?

Yes. /raw-data/export/app/{app_id}/installs/v5 returns a CSV of install records, /raw-data/export/app/{app_id}/in-app-events/v5 returns events, and /raw-data/export/app/{app_id}/uninstalls/v5 returns uninstalls. All accept from and to date parameters and respect the data-rate plan attached to the AppsFlyer account.

How do I send a server-to-server event to AppsFlyer?

POST /inappevent/{app_id} with the appsflyer_id (or customerUserId), eventName (e.g. af_purchase), eventValue, and eventCurrency. Use the API-key Authorization header. This is how backend-side conversions (subscription renewal, server-confirmed purchase) are credited to the original install.

What are the rate limits for the AppsFlyer API?

Raw data export endpoints are rate-limited to a small number of requests per minute per app (typically tens), while aggregate and S2S endpoints allow higher throughput. Bulk warehouse syncs should chunk by date and back off on 429 responses; do not try to export months of data in a single call.

How do I pull AppsFlyer attribution data through Jentic?

Search Jentic for 'AppsFlyer installs raw export', load /raw-data/export/app/{app_id}/installs/v5, and execute it with from=YYYY-MM-DD, to=YYYY-MM-DD, and additional_fields if needed. The response is a CSV that the agent can stream into the warehouse without holding the full file in memory.

Can I list every app in my AppsFlyer account?

Yes. GET /apps/v1.0/list returns the apps visible to the calling token along with their app_id, platform, and ownership metadata. Use this to power a dashboard selector or to iterate raw-data exports across every app in the account.

Can I limit what my agent is allowed to do with the AppsFlyer API?

Yes. Jentic One is self-hosted, so your own rules decide which AppsFlyer operations and credentials the agent may use. Because AppsFlyer carries the app id in the URL path, such as /raw-data/export/app/{app_id}/installs/v5, you can pin the agent to a single app so it exports only that app's attribution data. You also choose the exact operations it may call, so write actions like server-to-server event ingestion via POST /inappevent/{app_id} or user management on /v1.0/users are available only if you add them.