canonical: https://jentic.com/apis/adjust.com/adjust

# Adjust API

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.

## For AI agents

Pull mobile attribution KPIs and custom reports from Adjust for a given app token, including deliverable, tracker, event, and cohort metrics.

## Scope

Does not handle ad spend management, push notifications, or in-app messaging - use for retrieving mobile attribution KPIs and custom reports only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Deliverable KPIs** — Top-line metrics like installs, sessions, and revenue for an app token
- **Tracker KPIs** — Per-tracker performance metrics for acquisition source analysis
- **Event KPIs** — Volume and revenue for specific in-app events
- **Cohort KPIs** — Retention and LTV data by acquisition cohort
- **Reports** — Custom reports across dimensions and metrics for an app token

## Why Jentic

- **Setup:** Wiring the Adjust API by hand means handling its bearer token auth and threading your app_token into every KPI and report path. Through Jentic you install once, import Adjust from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Adjust puts the app_token in the URL path (/kpis/v1/{app_token}/...), so a rule can pin your agent to one app: it can read KPIs, trackers, events, and cohorts for that app and nothing else. Every operation on this surface is read-only, so the agent reports data without changing it.
- **Credential handling:** Your Adjust bearer token 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.
- **Discovery method:** Agents search Jentic by intent such as 'adjust cohort retention' or 'pull a custom report', and Jentic returns the matching Adjust operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Kochava API** — Mobile attribution and analytics platform with similar tracker-level reporting.
- **Facebook Graph API** — Source of paid acquisition spend that Adjust attributes to.
- **Mailchimp API** — Email and re-engagement campaigns that drive return visits measurable in Adjust.

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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.

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

Yes. Because you run Jentic One yourself, your own rules decide which Adjust operations and credentials the agent can use. Since Adjust puts the app_token in the URL path (/kpis/v1/{app_token}/...), a rule can pin your agent to a single app so it reads only that app's deliverable, tracker, event, and cohort KPIs and nothing else. Every operation on this surface is read-only, so the agent reports data without changing anything in your Adjust account.