Adjust API
★ Only Publicly Available OpenAPI DocumentAnalyticsProduct Analyticsbearer5 EndpointsREST
For Agents
Pull mobile attribution KPIs and custom reports from Adjust for a given app token, including deliverable, tracker, event, and cohort metrics.
Use for: I want to pull last week's installs and revenue for my app, Retrieve tracker KPIs for the iOS app's Facebook Ads source, Get the cohort retention curve for users acquired in March, List all event KPIs for the registration_complete event
Not supported: Does not handle ad spend management, push notifications, or in-app messaging — use for retrieving mobile attribution KPIs and custom reports only.
Jentic publishes the only available OpenAPI specification for Adjust API, keeping it validated and agent-ready. The Adjust API exposes 5 reporting endpoints for mobile attribution and analytics, returning deliverable, tracker, event, and cohort KPIs along with custom report data scoped per app token. Use it to pull retention, revenue, and ad-spend data for mobile apps without scraping the Adjust dashboard. Authentication is via a bearer token tied to the app account.
Install Jentic One Beta
Connect the Adjust API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adjust 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.
1
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 | sh2
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 instanceJentic 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 Adjust API.
Retrieve deliverable KPIs for a mobile app including installs, sessions, and revenue
Pull tracker-level KPIs to compare performance across acquisition sources
Fetch event KPIs for in-app conversion events such as registration or first purchase
Generate cohort KPIs for retention and lifetime value analysis by acquisition cohort
Run custom reports against any combination of dimensions and metrics for an app token
Use Cases
Patterns agents use Adjust API for, with concrete tasks.
★ Mobile Acquisition Reporting
Mobile growth teams pull tracker-level installs, sessions, and revenue data per app token using GET /kpis/v1/{app_token}/trackers without exporting CSVs from the Adjust UI. Numbers can be sliced by date range, country, and other dimensions exposed by the API. Setting up an automated daily report against this endpoint takes well under an hour.
Fetch tracker KPIs for app_token abc123 over the last 7 days grouped by country and return the top 10 trackers by installs
Cohort Retention Analysis
Product analysts pull retention and LTV data by acquisition cohort using GET /kpis/v1/{app_token}/cohorts. Outputs feed into BI tools or LLM-driven retention summaries without manual dashboard exports. Cohort definitions are configured in Adjust and the API returns the curve over a specified period range.
Pull cohort KPIs for app_token abc123 for cohorts acquired in March and return retention values at day 1, 7, and 30
Event-Level Conversion Tracking
Marketing teams measure the volume and revenue of specific in-app events (registration, purchase, level-completion) per tracker using GET /kpis/v1/{app_token}/events. This isolates which acquisition sources produce high-intent users rather than just installs.
Get event KPIs for the purchase event on app_token abc123 grouped by tracker for the last 30 days
Agent-Driven Mobile Analytics via Jentic
AI agents can call the Adjust reporting endpoints through Jentic to answer growth questions in natural language. The bearer token is held in Jentic's vault so the agent never sees the raw secret. Because the API only has 5 endpoints, intent search reliably resolves to the right call.
Search Jentic for 'adjust deliverable kpis', load GET /kpis/v1/{app_token}, and execute it for app_token abc123 with date range last_7_days
Key Endpoints
5 endpoints — jentic publishes the only available openapi specification for adjust api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/kpis/v1/{app_token}
Get deliverable KPIs for an app
GET
/kpis/v1/{app_token}/trackers
Get tracker-level KPIs
GET
/kpis/v1/{app_token}/events
Get event KPIs
GET
/kpis/v1/{app_token}/cohorts
Get cohort KPIs
GET
/reports/v1/{app_token}
Run a custom report
GET
/kpis/v1/{app_token}
Get deliverable KPIs for an app
GET
/kpis/v1/{app_token}/trackers
Get tracker-level KPIs
GET
/kpis/v1/{app_token}/events
Get event KPIs
GET
/kpis/v1/{app_token}/cohorts
Get cohort KPIs
GET
/reports/v1/{app_token}
Run a custom report
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Adjust bearer tokens are stored encrypted in the Jentic vault. The token authorises read access to all KPI data for your app, so Jentic ensures it never appears in the agent's prompt context.
Intent-based discovery
Agents search Jentic by intent (e.g., 'adjust cohort retention') and Jentic returns the matching KPI endpoint with its input schema. With only 5 endpoints, intent search resolves quickly and unambiguously.
Time to first call
Direct Adjust integration: half a day to a day for auth and parameter handling. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Adjust API through Jentic.
Why is there no official OpenAPI spec for Adjust API?
Adjust does not publish an OpenAPI specification for its KPI service. Jentic generates and maintains this spec from the published Adjust developer documentation so AI agents and developers can call it via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Adjust API use?
The Adjust API uses HTTP bearer authentication. The token is supplied in the Authorization header and is tied to your Adjust account's app token. Through Jentic, the bearer token is stored in the vault and injected at execution time so the agent never sees the raw secret.
Can I get cohort retention data with the Adjust API?
Yes. GET /kpis/v1/{app_token}/cohorts returns retention and LTV curves grouped by acquisition cohort. Cohort definitions are configured inside Adjust and the API returns the time-series for a given app_token and date range.
How do I pull tracker-level installs with the Adjust API through Jentic?
Search Jentic for 'adjust tracker kpis', load GET /kpis/v1/{app_token}/trackers, and execute it with your app_token and date range. Jentic returns the input schema so the agent supplies only the parameters Adjust accepts.
What are the rate limits for the Adjust API?
The OpenAPI spec does not publish numeric rate limits. Adjust applies fair-use limits server-side; HTTP 429 responses indicate throttling. Through Jentic, retries with backoff can be configured in the execution request.
Can I run custom multi-dimension reports with the Adjust API?
Yes. GET /reports/v1/{app_token} accepts dimensions and metrics parameters so you can build cross-cuts (e.g., installs by country and tracker) without composing four separate KPI calls.
GET STARTED