# Jampp

> Jampp is a programmatic demand-side platform for mobile app growth, founded in 2013 and now an Affle company. It buys user acquisition, app retargeting and CTV inventory for app advertisers in commerce, fintech, gaming and delivery. Its one public developer surface is the Jampp Reporting API — a GraphQL endpoint returning funnel metrics (impressions, clicks, installs, in-app events, spend, CPI/CPA/ROAS) grouped across ~71 campaign, creative, geo, publisher and SKAdNetwork dimensions.

Generated by API Evangelist on 2026-08-12. Jampp serves no llms.txt of its own (https://developers.jampp.com/llms.txt returns 404); this file is generated from the provider's published documentation and from artifacts in the api-evangelist/jampp profile.

## APIs

- [Jampp Reporting API](https://developers.jampp.com/docs/reporting-api/): GraphQL reporting for Jampp advertisers. Endpoint `https://reporting-api.jampp.com/v1/graphql`. Operations: `pivot`, `asyncPivot`, `asyncPivots`, `postbackShare` (queries) and `createAsyncPivot` (mutation).

## Authentication

- [Token endpoint](https://auth.jampp.com/v1/oauth/token): OAuth 2.0 client credentials, form-encoded (`grant_type=client_credentials`, `client_id`, `client_secret`). Returns a Bearer token valid 7200 seconds. Send as `Authorization: Bearer {access_token}`.
- [Issue API keys](https://app.jampp.com/users/credentials): client id / secret pairs are minted by a signed-in user in the Silver dashboard. One pair per integrating service so each can be revoked independently.
- [Authorization server metadata](https://auth.jampp.com/.well-known/oauth-authorization-server): RFC 8414 document. Also advertises an authorization-code flow with PKCE S256 and dynamic client registration, neither of which is documented for developers.
- [JWKS](https://auth.jampp.com/.well-known/jwks.json): two ES256 keys (secp256k1), kid `v1` and `v2`.

## Docs

- [Developer portal](https://developers.jampp.com/docs/)
- [Reporting API reference](https://developers.jampp.com/docs/reporting-api/): the complete GraphQL type, query and mutation reference.
- [Python client docs](https://developers.jampp.com/docs/reporting-api-client/)
- [Python client usage](https://developers.jampp.com/docs/reporting-api-client/usage.html)
- [Python client changelog](https://developers.jampp.com/docs/reporting-api-client/changelog.html)

## SDKs

- [jampp_reporting_api_client on PyPI](https://pypi.org/project/jampp-reporting-api-client/): `pip install jampp_reporting_api_client` (add `[pandas]` for DataFrame results). Version 0.3.2, published 2026-06-01. Source at https://github.com/jampp/reporting-api-client.

## Behaviour an agent needs to know

- Jampp's own docs print the endpoint as `https://reporting-api.com/graphql`. That is not a Jampp host. Use `https://reporting-api.jampp.com/v1/graphql`.
- GraphQL introspection is auth-gated: an anonymous POST returns `401 {"error":"Neither Cookie nor Authorization present."}`. The public schema is the HTML reference, not an introspectable endpoint.
- There is no pagination. Large results go through `createAsyncPivot`, then poll `asyncPivot(pivotId)` until status is `READY` and download the signed CSV at `.url`. Statuses: PENDING, QUEUED, RUNNING, READY, UP_FOR_RETRY, FAILED.
- There is no idempotency key. A retried `createAsyncPivot` creates a duplicate job with a new UUID.
- No rate limit is published and no rate-limit headers are returned. The published limits are structural: HOURLY granularity only for the last 15 days; `siteBundle` only for the last 3 months; `siteName`/`siteBundle` cannot be combined with `region`, `city`, `dma`, `zipCode`, `ad` or `adId`.
- Errors are not RFC 9457 and carry no stable codes. `reporting-api` returns `{"error": "<string>"}`; `auth` returns `{"error": {"message": "<string>"}}`.
- No status page, no SLA, no deprecation policy, no API changelog, no sandbox, no webhooks, no MCP server, no A2A agent card.
- No published pricing. Jampp is sold through sales; the API is an entitlement of an advertiser account.

## Artifacts (API Evangelist profile)

- [apis.yml](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/apis.yml)
- [Authentication](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/authentication/jampp-authentication.yml)
- [OAuth scopes](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/scopes/jampp-scopes.yml)
- [Conventions](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/conventions/jampp-conventions.yml)
- [Error catalog](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/errors/jampp-problem-types.yml)
- [Lifecycle](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/lifecycle/jampp-lifecycle.yml)
- [Rate limits](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/rate-limits/jampp-rate-limits.yml)
- [Reporting vocabulary](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/vocabulary/jampp-reporting-vocabulary.yml)
- [Data model](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/data-model/jampp-data-model.yml)
- [Conformance](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/conformance/jampp-conformance.yml)
- [Well-known index](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/well-known/jampp-well-known.yml)
- [Packages](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/packages/jampp-packages.yml)
- [Agent skills](https://raw.githubusercontent.com/api-evangelist/jampp/refs/heads/main/skills/_index.yml)

## Company

- [Website](https://jampp.com/)
- [About](https://www.jampp.com/about)
- [Blog](https://www.jampp.com/blog)
- [Contact](https://www.jampp.com/contact)
- [GitHub](https://github.com/jampp)
- [Advertiser terms](https://www.jampp.com/advertisers-terms-and-conditions)
- [Publisher terms](https://www.jampp.com/publishers-terms-and-conditions)
- [Privacy policy](https://www.jampp.com/privacy-policy-terms-and-conditions)
- Support: productsupport@jampp.com · Data privacy: dataprivacy@jampp.com