Skip to content

Adfin API (1.0.0)

Adfin uses OAuth 2.0 access tokens to authenticate all API requests.

There are two contexts in which tokens are issued:

  • Biller Access Tokens — Generated via the Authorization Code flow when a biller connects their Adfin account. These tokens grant access to that biller's data (invoices, payment requests, customers, etc.).

  • Platform Access Tokens — Generated via the Client Credentials flow for Adfin's own integrations and system events. These tokens authenticate Adfin as the platform itself (not as a specific biller) and are required for endpoints like /api/webhook.

Download OpenAPI description
partner-integration-api-reference.json
partner-integration-api-reference.yaml
Languages
Servers
Mock server
https://developer.adfin.com/_mock/products/partner-integration/partner-integration-api-reference/
Production API Server URL
https://api.adfin.com/api/
Staging API Server URL
https://api.staging.adfin.com/api/

oAuth2

Operations

Biller

Operations

Customers

Operations

Direct debit mandates

Operations

Invoices

Operations

Recurring invoices

Operations

Payment requests

Operations

Recurring payment requests

Operations

Payments

Operations

Tax rates

Operations

Items

Operations

Get line item catalogue items for a given filter

Request

Security
Biller Access Token (Production) or Biller Access Token (Staging)
Query
descriptionstring

Item description

curl -i -X GET \
  'https://developer.adfin.com/_mock/products/partner-integration/partner-integration-api-reference/catalogs/items?description=string' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Responses

The request has succeeded and has resulted in one line item catalogue element created

Bodyapplication/json
itemsArray of objects(LineItemCatalogueResponse)

The list of line items catalogue

Response
application/json
{
  "items": [
    { … }
  ]
}

Workflows

Operations

Webhooks

Operations