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

# Nets Data Suite API

Jentic publishes the only available OpenAPI specification for Nets Data Suite API, keeping it validated and agent-ready. Nets Data Suite gives merchants and acquirers structured access to transaction-level analytics and reporting on the Nets payment estate. The API exposes two endpoints - transactions and reports - that let downstream systems pull settlement data and aggregated reports for reconciliation, fraud analytics, and finance dashboards.

## For AI agents

Pull transaction-level data and aggregated reports from the Nets Data Suite analytics backend.

## Scope

Does not handle payment authorisation, refund processing, or merchant onboarding - use for transaction-level analytics and reporting on Nets-acquired traffic only.

## Capabilities

- Pull transaction-level records for finance reconciliation
- Generate or fetch aggregated payment reports for a date range
- Feed Nets settlement data into a BI warehouse
- Cross-check internal order records against Nets transaction state
- Power a finance dashboard reading directly from Nets

## Use cases

### Daily Transaction Reconciliation

Pull yesterday's transactions from Nets Data Suite each morning and reconcile them against internal order records. Variances flagged automatically save finance teams hours of manual checking and surface acquirer-side anomalies (chargebacks, late settlements) faster than dashboard browsing.

Example prompt: Fetch /transactions for date 2026-06-10, join against internal orders, and return any orders missing a matching Nets transaction.

### Finance Reporting Pipeline

Stream Nets reports into a data warehouse on a schedule so analysts can query them in SQL alongside other revenue sources. The /reports endpoint exposes aggregated views suitable for time-series charts and KPI calculation without re-aggregating raw transactions.

Example prompt: Fetch /reports for the previous calendar month and load the result into the finance.payments_monthly table in the data warehouse.

### AI Agent Finance Q&A

Let an AI agent answer 'how much did we settle yesterday on Nets?' or 'show me transactions over 1k EUR' through Jentic. The agent calls /transactions or /reports, summarises in plain English, and links back to source rows for audit.

Example prompt: Given the question 'what was our Nets settlement total last week?', fetch /reports for the relevant range and return total volume and transaction count.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/transactions` | List transactions with filters |
| GET | `/reports` | Fetch aggregated reports |

## Key resources

- **Transactions** — Transaction-level records from the Nets payment estate
- **Reports** — Aggregated reports on volume, settlement, and merchant activity

## Why Jentic

- **Setup:** Wiring the Nets Data Suite API by hand means setting its Authorization API key header, targeting the api.netsdatasuite.com host, and shaping transaction and report queries yourself. Through Jentic you install once, import Nets Data Suite from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Nets Data Suite is a read API whose filters travel in the request, so limit the agent to the operations it needs, such as listing transactions or pulling a report, and leave out the ones it should not run.
- **Credential handling:** Your Nets Data Suite 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 'pull yesterday's Nets settlements' or 'report on acquired traffic', and Jentic returns the matching Data Suite operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe API** — Stripe's reporting endpoints expose comparable transaction-level data on its own acquiring stack.
- **Adyen Balance Control API** — Adyen's reporting and balance APIs cover similar reconciliation use cases on Adyen-acquired traffic.
- **Nets API Marketplace** — Nets API Marketplace creates the payments that Nets Data Suite later reports on.

## FAQ

### Why is there no official OpenAPI spec for the Nets Data Suite API?

Nets does not publish a public OpenAPI specification for the Data Suite backend. Jentic generates and maintains this spec so that AI agents and developers can call Nets Data Suite 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 Nets Data Suite API use?

The Nets Data Suite API uses API key authentication. The key is provisioned by Nets when you enable Data Suite reporting on your acquiring contract and is passed in a request header. Through Jentic the key is stored encrypted and never exposed to the agent context.

### Can I pull individual transactions from the Nets Data Suite API?

Yes. GET /transactions returns transaction-level records that can be filtered by date and other parameters. Use it for line-by-line reconciliation against internal order records.

### What are the rate limits for the Nets Data Suite API?

Nets does not publish a public rate limit on Data Suite endpoints; throughput is governed by your Data Suite plan. Reporting calls are heavier than transaction fetches, so schedule report pulls outside peak settlement windows.

### How do I pull a daily settlement report through Jentic?

Run jentic.search('get nets data suite report'), load the matching operation, and execute GET /reports with the date range parameters. Jentic returns the aggregated payload ready for the agent to summarise or load into a warehouse.

### Does Nets Data Suite return historical data or only the most recent period?

Both /transactions and /reports support date-range filters. Historical depth depends on your Data Suite plan, but most acquirer contracts retain at least 13 months of data for reconciliation.

### Can I limit what my agent is allowed to do with the Nets Data Suite API?

Yes. Because you run Jentic One yourself, your own rules decide which Nets Data Suite operations the agent may call and which credentials it may use. This API is read-only with just two operations, listing transactions via GET /transactions and pulling aggregated reports via GET /reports, so you can allow only the one the agent needs and leave the other out. Your Nets Data Suite API key stays with your self-hosted instance and is injected only for the operations you have permitted.