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

# Awin API

Jentic publishes the only available OpenAPI specification for Awin API, keeping it validated and agent-ready. The Awin API exposes the affiliate marketing network's core reporting and management surface for both publishers and advertisers, including transactions, performance reports, programme data, commission groups, and account profile lookups. Authentication uses a bearer token (Awin OAuth API token) and the spec covers seven endpoints scoped by publisherId, advertiserId, and account.

## For AI agents

Pull affiliate transactions and performance reports for publishers and advertisers, list programmes, and inspect commission groups in the Awin affiliate network.

## Scope

Does not handle creative or banner asset hosting, link-tracking redirects, or payouts - use for affiliate transaction and report retrieval and programme inspection only.

## Capabilities

- List publisher transactions with filters for date range, status, and advertiser via `/publishers/{publisherId}/transactions`
- Pull publisher-side performance reports across advertisers and date ranges
- List the affiliate programmes a publisher is joined to or has applied to
- Inspect a programme's commission groups to understand how each conversion is paid
- Mirror the same transaction and report endpoints on the advertiser side under `/advertisers/{advertiserId}`
- Look up the calling user's Awin accounts (publisher and advertiser memberships) via /accounts

## Use cases

### Publisher Earnings Reconciliation

Affiliate publishers reconcile Awin earnings against their internal click and conversion data by pulling `/publishers/{publisherId}/transactions` for a given period. The endpoint returns confirmed, pending, and declined transactions with click reference, sale amount, and commission, replacing manual CSV exports from the Awin dashboard.

Example prompt: Call GET `/publishers/{publisherId}/transactions` with startDate and endDate covering the previous calendar month, filter status to 'approved', and sum commissionAmount per advertiser

### Advertiser Performance Reporting

Advertisers monitor their affiliate programme by pulling `/advertisers/{advertiserId}/reports` to surface clicks, conversions, sales, and commission paid by publisher and timeframe. The data feeds dashboards and spend allocation decisions, removing the lag of waiting on a weekly Awin email.

Example prompt: Call GET `/advertisers/{advertiserId}/reports` for the last 30 days grouped by publisher and return the top five publishers by total sale amount

### Programme and Commission Inspection

Affiliate-management agents inspect `/publishers/{publisherId}/programmes` and `/publishers/{publisherId}/commissiongroups` to understand which advertisers a publisher is joined to and how each commission group pays out. This supports automated outreach, programme application reviews, and yield optimisation.

Example prompt: List programmes for publisher {id}, pull commission groups for each, and return any programme whose top commission rate exceeds 10%

### Agent-Driven Affiliate Operations via Jentic

Performance-marketing agents call the Awin API through Jentic to monitor transactions, surface anomalies, and report to revenue teams without standing up a custom Awin connector. Jentic exposes the seven Awin endpoints as discoverable tools so the agent picks publisher-side or advertiser-side operations based on the user's role.

Example prompt: Search Jentic for 'list Awin transactions', load the schema for GET `/publishers/{publisherId}/transactions`, and execute for the last 7 days, then summarise total commission and any declined transactions

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/accounts` | List Awin accounts for the calling user |
| GET | `/publishers/{publisherId}/transactions` | List publisher transactions |
| GET | `/publishers/{publisherId}/reports` | Pull publisher performance reports |
| GET | `/publishers/{publisherId}/programmes` | List programmes for a publisher |
| GET | `/publishers/{publisherId}/commissiongroups` | List commission groups for a publisher |
| GET | `/advertisers/{advertiserId}/transactions` | List advertiser transactions |
| GET | `/advertisers/{advertiserId}/reports` | Pull advertiser performance reports |

## Key resources

- **Accounts** — Look up the publisher and advertiser accounts associated with the calling user
- **Publisher Transactions and Reports** — Transactions and performance reports for publishers
- **Advertiser Transactions and Reports** — Transactions and performance reports for advertisers
- **Programmes and Commission Groups** — Programmes a publisher is joined to and the associated commission groups

## Why Jentic

- **Setup:** Wiring the Awin API by hand means attaching a bearer token on every call, resolving your publisher or advertiser account id, and handling date-windowed pagination across transaction and report routes. Through Jentic you install once, import the Awin API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** Awin puts the account id in the URL path, such as `/publishers/{publisherId}/transactions` and `/advertisers/{advertiserId}/reports`, so a rule can pin the agent to one publisher or advertiser account. You choose which operations it may call, such as retrieving transactions or reports, so it reads only the sides and data you allow.
- **Credential handling:** Your Awin 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 'list affiliate transactions' or 'pull a programme report', and Jentic returns the matching Awin operation, publisher- or advertiser-side, with its path-parameter schema so the agent supplies the correct account id without browsing the reference docs.

## Related APIs

- **Shopify Admin** — Reconcile Awin affiliate transactions against Shopify orders to confirm conversions and refunds.
- **Stripe** — Match Stripe charges and refunds with Awin's reported sales to detect refund-driven commission clawbacks.
- **Google Analytics** — Combine Awin's affiliate channel data with Analytics for a multi-channel view of acquisition.

## FAQ

### Why is there no official OpenAPI spec for Awin API?

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

The Awin API uses a bearer token (the OAuth API token issued in the Awin dashboard). Send it as 'Authorization: Bearer <token>'. Through Jentic, the token lives in your Jentic One instance and is attached to each request automatically - agents never see the raw token.

### Can I pull all my affiliate transactions with the Awin API?

Yes. GET `/publishers/{publisherId}/transactions` returns transactions for a publisher and GET `/advertisers/{advertiserId}/transactions` returns the advertiser-side view. Both accept date-range parameters so you can window-load data for reconciliation.

### What are the rate limits for the Awin API?

Awin enforces a per-token rate limit of around 20 requests per minute for the reporting endpoints; transaction endpoints are stricter still and expect bulk windowed pulls rather than per-row queries. Watch for HTTP 429 responses and back off on the Retry-After header.

### How do I find my publisherId or advertiserId through Jentic?

Search Jentic for 'list Awin accounts', load the schema for GET /accounts, and execute. The response lists every account the bearer token has access to with its accountId and accountType, so subsequent calls can plug the right ID into the path.

### Is the Awin API free for publishers and advertisers?

Awin includes API access with active publisher and advertiser accounts; there is no separate per-call fee. You do need an active Awin account in good standing and an OAuth API token generated from the Awin dashboard.

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

Yes. Because you run Jentic One yourself, your own rules decide which Awin operations and credentials the agent may use. Awin puts the account id in the URL path, such as `/publishers/{publisherId}/transactions` and `/advertisers/{advertiserId}/reports`, so a rule can pin the agent to a single publisher or advertiser account. You also choose which operations it may call, for example retrieving transactions or reports but not listing programmes, so it reads only the sides and data you allow.