Awin API

Name: Awin API API
Brand: Awin API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingAdvertisingbearer7 EndpointsREST

For Agents

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

Quickstart

Get started with Awin API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list Awin affiliate transactions"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Awin API API.

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

GET STARTED

Start building with Awin API API

Explore with Jentic

View OpenAPI Document

Use for: I want to pull all confirmed affiliate transactions for May 2026, Get last week's performance report for publisher 12345, List all programmes my publisher account is joined to, Check the commission groups for advertiser programme 6789

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

Jentic publishes the only available OpenAPI document for Awin API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Awin API API for, with concrete tasks.

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

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.

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.

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.

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

7 endpoints — jentic publishes the only available openapi specification for awin api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Awin OAuth bearer tokens are stored encrypted in the Jentic vault. Jentic attaches the bearer header on each call and never exposes the raw token to the agent.

Intent-based discovery

Agents search by intent (e.g., 'list affiliate transactions') and Jentic returns the matching Awin operation — publisher- or advertiser-side — with the full path-parameter schema so the agent supplies the correct ID.

Time to first call

Direct Awin integration: 1-2 days for token wiring, account ID resolution, and date-windowed pagination. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Shopify Admin

Reconcile Awin affiliate transactions against Shopify orders to confirm conversions and refunds.

Use Shopify when the underlying order data is needed to validate or adjust an Awin transaction.

Complementary

Stripe

Match Stripe charges and refunds with Awin's reported sales to detect refund-driven commission clawbacks.

Use Stripe when payment-level reconciliation is required alongside affiliate reporting.

Complementary

Google Analytics

Combine Awin's affiliate channel data with Analytics for a multi-channel view of acquisition.

Use Analytics when you need to compare Awin's affiliate performance against other paid and organic channels.

FAQs

Specific to using Awin API API through Jentic.

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 at https://app.jentic.com/sign-up.

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 the Jentic vault 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.