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

# Kochava Publisher API

Jentic publishes the only available OpenAPI specification for Kochava Publisher API, keeping it validated and agent-ready. Kochava is a mobile measurement and attribution platform used by app marketers to track installs, in-app events, and ad performance across networks. The publisher REST API exposes the apps registered to a publisher, the campaigns that drive installs, and the trackers that route attribution data, so an analytics or marketing engineer can manage the Kochava configuration without using the dashboard. It suits app teams that operate at scale and want to script tracker provisioning across many campaigns.

## For AI agents

Manage Kochava apps, campaigns, and trackers programmatically to control mobile attribution configuration.

## Scope

Does not handle raw event-level attribution data, fraud reports, or SDK install-time integration - use for managing Kochava apps, campaigns, and trackers only.

## Capabilities

- List the apps registered under a Kochava publisher account
- Retrieve a single Kochava app to inspect its configuration
- Create a Kochava campaign for a specific app
- Update a Kochava campaign with new attribution windows or partners
- Provision a Kochava tracker that routes installs and events
- Inspect a tracker by id to confirm parameters before launch

## Use cases

### Tracker Provisioning at Scale

Provision Kochava trackers for many ad networks programmatically instead of clicking through the dashboard. The /v1/trackers endpoint lists existing trackers and accepts the configuration needed to create new ones, while /v1/campaigns lets the marketer group those trackers logically. Best for app teams running dozens of campaigns and adding new partner networks every quarter.

Example prompt: For each ad partner in the launch sheet, POST to /v1/trackers under campaign id 42 and store the returned tracker URLs back in the sheet.

### Campaign Configuration Audit

Audit existing Kochava campaign configuration before a major launch. /v1/campaigns and /v1/campaigns/{campaignId} together expose the campaign metadata, attribution windows, and partner mapping needed to spot misconfigurations early. Useful for performance marketing leads inheriting an account from a previous agency.

Example prompt: List Kochava campaigns and report any whose attribution window is shorter than 7 days for review.

### App Inventory Sync

Keep an internal app inventory in sync with what is registered in Kochava. /v1/apps lists all apps under a publisher account and /v1/apps/{appId} returns the per-app detail. Useful for ops teams that maintain a central registry of mobile apps across regions and need it to match the source of truth in Kochava.

Example prompt: List all Kochava apps via GET /v1/apps and produce a CSV of app id, name, and platform.

### Agent-Driven Marketing Operations via Jentic

Have an AI agent answer marketing-ops questions like 'create a tracker for partner X under campaign Y' or 'list active campaigns' by calling Kochava through Jentic. The agent searches Jentic for the matching publisher operation, loads the schema, and executes with the API key kept in your Jentic One instance. Removes the dashboard click-through from a fast-moving launch.

Example prompt: Through Jentic, search for 'list Kochava campaigns', load /v1/campaigns, and report the count of active campaigns.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/apps | List apps under the publisher |
| GET | /v1/apps/{appId} | Retrieve an app |
| GET | /v1/campaigns | List campaigns |
| GET | /v1/campaigns/{campaignId} | Retrieve a campaign |
| GET | /v1/trackers | List trackers |
| GET | /v1/trackers/{trackerId} | Retrieve a tracker |

## Key resources

- **Apps** — Apps registered under the publisher account
- **Campaigns** — Campaigns that group trackers for an app
- **Trackers** — Tracker URLs that route installs and events for attribution

## Why Jentic

- **Setup:** Wiring the Kochava Publisher API by hand means learning its Authentication-Key header auth and handling the api.kochava.com host and its errors yourself. Through Jentic you install once, import Kochava from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Kochava puts the app id in the URL path (/v1/apps/{appId}), so a rule can pin your agent to one app: it can read that app and its campaigns and trackers and nothing else. Every operation here is a read, so you choose which of those the agent may call.
- **Credential handling:** Your Kochava 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.
- **Discovery method:** Agents search Jentic by intent such as 'list Kochava apps' or 'read a campaign's trackers', and Jentic returns the matching Kochava operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Adjust API** — Mobile measurement partner with similar app, campaign, and tracker model
- **Amplitude API** — Product analytics platform that pairs with Kochava attribution
- **Mixpanel API** — Product analytics for retention and funnel measurement after install

## FAQ

### Why is there no official OpenAPI spec for Kochava Publisher API?

Kochava does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Kochava Publisher API 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 Kochava Publisher API use?

The Kochava Publisher API uses an API key sent in the Authentication-Key header on every request. Through Jentic, the API key is stored in your Jentic One instance and injected at execution time so the agent never holds the raw value.

### Can I create a tracker through the Kochava Publisher API?

Yes. /v1/trackers exposes the trackers under the publisher account and supports the writes needed to create a new tracker bound to a campaign. Use it to provision per-partner attribution links without opening the dashboard.

### What are the rate limits for the Kochava Publisher API?

Kochava does not publish a public rate limit and the spec does not declare one. Treat list endpoints as moderately throttled and avoid tight polling on /v1/campaigns or /v1/trackers; cache where the data changes infrequently.

### How do I list Kochava campaigns from an AI agent through Jentic?

Search Jentic for 'list Kochava campaigns', load GET /v1/campaigns, and execute. Jentic injects the Authentication-Key header from the vault and the agent receives the campaign list with id and metadata.

### Does this API include raw event-level attribution data?

No. This publisher API covers configuration of apps, campaigns, and trackers. Raw install and event data are surfaced through Kochava's reporting and attribution feeds, which are separate from this management surface.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Kochava operations and which API key your agent may use. Kochava puts the app id in the URL path (/v1/apps/{appId}), so a rule can pin the agent to a single app and let it read only that app and its related campaigns and trackers. Every operation on this API is a read, such as GET /v1/apps, GET /v1/campaigns, and GET /v1/trackers, so you choose exactly which of those the agent is allowed to call.