Install Jentic One Beta

Connect the Awin API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Awin API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fawin.com%2Fawin" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fawin.com%2Fawin" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Awin 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

Mirror the same transaction and report endpoints on the advertiser side under /advertisers/{advertiserId}

GET STARTED

Start building with Awin API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Awin 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

GET

/advertisers/{advertiserId}/transactions

List advertiser transactions

GET

/advertisers/{advertiserId}/reports

Pull advertiser performance reports

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Awin 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 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.

Awin API

Name: Awin API
Brand: Awin API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticMarketingAdvertisingbearer7 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

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

Jentic One on Github View OpenAPI Document