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

# NetRefer Operator API

Jentic publishes the only available OpenAPI specification for NetRefer Operator API, keeping it validated and agent-ready. NetRefer is an affiliate and partner marketing platform used heavily in regulated industries such as iGaming. The Operator API ingests affiliate registrations, player events, and financial transactions, then exposes a performance reporting endpoint operators can use to reconcile commissions. Use it to wire backend systems into NetRefer's commission engine without manual CSV uploads.

## For AI agents

Push affiliate, player, and transaction data into NetRefer and pull back partner performance reports for an operator account.

## Scope

Does not handle player KYC, payment processing, or affiliate creative asset hosting - use for affiliate ingestion, attribution, and operator-side commission reporting only.

## Capabilities

- Register a new affiliate or partner against an operator brand
- Stream player registration events with referring affiliate attribution
- Push financial transactions (deposits, wagers, payouts) for commission calculation
- Update commission terms on an existing affiliate relationship
- Pull a performance report for a date range across affiliates

## Use cases

### Real-Time Affiliate Attribution

Send player registration and deposit events to NetRefer the moment they happen so commissions are calculated against the correct affiliate. The Operator API accepts player and transaction events with affiliate identifiers, removing the latency and reconciliation pain of nightly batch uploads.

Example prompt: POST a player signup for player P-555 with referring affiliate A-123 to `/api/v1/players`, then post a deposit of 100 EUR for that player to `/api/v1/transactions.`

### Operator Commission Reporting

Pull a structured performance report covering registrations, deposits, and payouts attributed to each affiliate for a date range. Operators use it to reconcile affiliate invoices, audit commission accuracy, and feed partner-facing dashboards.

Example prompt: Fetch `/api/v1/reports/performance` for affiliate A-123 between 2026-05-01 and 2026-05-31 and return total commission earned.

### Partner Onboarding Automation

When a partnerships team approves a new affiliate in their CRM, an automation creates the matching record in NetRefer through `/api/v1/affiliates` with default commission terms. Eliminates manual double entry and ensures attribution starts the day the partner goes live.

Example prompt: Create an affiliate named 'Acme Marketing' with email partner@acme.com and the default revenue-share commission template, then return the new affiliate id.

### AI Agent Performance Q&A

Let an AI agent answer ad-hoc partnerships questions like 'how much did affiliate X earn last quarter?' or 'is yesterday's data ingested?' by hitting NetRefer through Jentic. Particularly useful for ops teams that don't want to give every analyst access to the NetRefer dashboard.

Example prompt: Given the question 'how did affiliate A-99 perform last week?', call the performance report endpoint and summarise registrations, deposits, and commission in plain English.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v1/affiliates` | Register a new affiliate |
| POST | `/api/v1/players` | Push a player event with affiliate attribution |
| POST | `/api/v1/transactions` | Push a financial transaction for commission calculation |
| POST | `/api/v1/commissions` | Update commission terms for an affiliate |
| GET | `/api/v1/reports/performance` | Pull a performance report for a date range |

## Key resources

- **Affiliates** — Affiliate and partner records under an operator brand
- **Players** — End-user accounts referred by affiliates
- **Transactions** — Financial events used for commission calculation
- **Commissions** — Commission term overrides per affiliate
- **Reports** — Performance report pulls across affiliates and date ranges

## Why Jentic

- **Setup:** Wiring the NetRefer Operator API by hand means setting its Authorization API key header, targeting the api.netrefer.com host, and shaping affiliate, player, transaction, and commission payloads yourself. Through Jentic you install once, import NetRefer from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** NetRefer takes its targets in the request body rather than the URL path, so limit the agent to the operations it needs, such as posting a transaction or reading the performance report, and leave out the ones it should not run.
- **Credential handling:** Your NetRefer 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 'push a player event with affiliate attribution' or 'pull operator commission reporting', and Jentic returns the matching NetRefer operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe API** — Stripe captures the underlying financial transactions; NetRefer attributes them to affiliates for commission.
- **HubSpot CRM Contacts API** — HubSpot stores partner relationships; NetRefer turns them into commissioned affiliates.
- **Drift API** — Drift captures partner-driven leads that NetRefer can attribute when they convert.

## FAQ

### Why is there no official OpenAPI spec for NetRefer Operator API?

NetRefer does not publish an OpenAPI specification on a public developer portal. Jentic generates and maintains this spec so that AI agents and developers can call NetRefer Operator 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 NetRefer Operator API use?

The NetRefer Operator API uses API key authentication. The key is passed in a request header issued to your operator account. Through Jentic the key is stored in the encrypted vault and never enters the agent context.

### Can I push player events in real time with the NetRefer API?

Yes. POST `/api/v1/players` accepts player registration events with referring affiliate identifiers. Pair it with POST `/api/v1/transactions` to push deposits, wagers, and payouts as they happen so commission calculation is up to date.

### What are the rate limits for the NetRefer Operator API?

NetRefer does not publish a public rate limit; ingestion throughput is governed by the contract on your operator account. For high-volume gaming traffic, batch your transaction posts and confirm SLA limits with your account manager.

### How do I pull a commission report through Jentic?

Run jentic.search('get netrefer affiliate performance report'), load the matching operation, then execute GET `/api/v1/reports/performance` with the affiliate id and date range. Jentic returns the structured report ready for downstream summarisation.

### Can I update commission terms for an existing affiliate?

Yes. POST `/api/v1/commissions` accepts a commission template change for a specific affiliate, letting you switch revenue share, CPA, or hybrid terms without recreating the affiliate record.

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

Yes. Jentic One is self-hosted, so you run it yourself and your own rules decide which NetRefer operations and credentials the agent can use. You can allow only the calls it needs, such as GET `/api/v1/reports/performance` to read commission reports, while withholding write operations like POST `/api/v1/affiliates`, POST `/api/v1/players`, POST `/api/v1/transactions`, and POST `/api/v1/commissions.` Because NetRefer takes its targets in the request body rather than the URL path, scoping happens at the operation level, and your stored API key is injected at execution time without ever entering the agent's context.