Debitura

Debitura is an API-first international debt collection platform covering cross-border B2B and B2C receivables. It publishes three separate public REST APIs, one per role in the network rather than one API with role-gated endpoints: the Customer API for creditors uploading invoices to collection and tracking cases, the Referral Partner API for platforms embedding collection as a referral and tracking revenue share, and the Collection Partner API for collection agencies operating cases on the platform. All three are OpenAPI 3.0.4, each on its own host, and each authenticates with an API key in the XApiKey header; the Customer API additionally accepts a bearer token, and the Referral Partner API exposes OAuth operations for minting them. Webhooks appear in all three, each with a paired test surface for exercising events before going live. Debitura publishes its own APIs.json at docs.debitura.com, which is how this profile was built.

Debitura publishes 3 APIs on the APIs.io network: Customer API, Referral Partner API, and Collection Partner API. Tagged areas include Debt Collection, Accounts Receivable, Debt Recovery, FinTech, and Payments.

18.8/100 emerging ▬ flat Agent 32/100 agent aware Full breakdown ↓
scored 2026-08-05 · rubric v0.9.1
3 APIs
Debt CollectionAccounts ReceivableDebt RecoveryFinTechPaymentsInvoicingWebhooks

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-05 · rubric v0.9.1
Composite quality — 18.8/100 · emerging
Contract Quality 15.1 / 25
Developer Ergonomics 0.0 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 7.0 / 10
Agent readiness — 32/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/debitura: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Debitura Customer API

For creditors. Uploading B2B and B2C invoices to collection, then tracking cases, contracts, payments and tasks through recovery. 53 operations across 44 paths, OpenAPI 3.0.4 wi...

Debitura Referral Partner API

For platforms embedding collection as a referral. Setting up clients, previewing cases, tracking revenue share, and minting bearer tokens through OAuth operations. 22 operations...

Debitura Collection Partner API

For collection agencies operating cases on the platform. Managed cases, bulk ingestion jobs, and the user and webhook surface behind them. 48 operations across 38 paths, OpenAPI...

Source (apis.yml)

apis.yml Raw ↑
name: Debitura
description: 'Debitura is an API-first international debt collection platform covering cross-border B2B and B2C receivables.
  It publishes three separate public REST APIs, one per role in the network rather than one API with role-gated endpoints:
  the Customer API for creditors uploading invoices to collection and tracking cases, the Referral Partner API for platforms
  embedding collection as a referral and tracking revenue share, and the Collection Partner API for collection agencies operating
  cases on the platform. All three are OpenAPI 3.0.4, each on its own host, and each authenticates with an API key in the
  XApiKey header; the Customer API additionally accepts a bearer token, and the Referral Partner API exposes OAuth operations
  for minting them. Webhooks appear in all three, each with a paired test surface for exercising events before going live.
  Debitura publishes its own APIs.json at docs.debitura.com, which is how this profile was built.'
url: https://debitura.apievangelist.com/apis.yml
created: '2026-08-01'
modified: '2026-08-01'
specificationVersion: '0.21'
tags:
- Debt Collection
- Accounts Receivable
- Debt Recovery
- FinTech
- Payments
- Invoicing
- Webhooks
apis:
- name: Debitura Customer API
  description: For creditors. Uploading B2B and B2C invoices to collection, then tracking cases, contracts, payments and tasks
    through recovery. 53 operations across 44 paths, OpenAPI 3.0.4 with 81 component schemas. Authenticates with an API key
    in the XApiKey header or a bearer token. Carries webhooks with a paired test-webhook and test-case surface.
  humanURL: https://docs.debitura.com/clients
  baseURL: https://customer-api.debitura.com
  tags:
  - Debt Collection
  - Accounts Receivable
  - Invoicing
  - Payments
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/debitura-customer-api.json
  - type: OpenAPI
    url: https://docs.debitura.com/openapi/customer-api.json
  - type: Documentation
    url: https://docs.debitura.com/clients
  - type: SignUp
    url: https://app.debitura.com/CreditorApiKey
- name: Debitura Referral Partner API
  description: For platforms embedding collection as a referral. Setting up clients, previewing cases, tracking revenue share,
    and minting bearer tokens through OAuth operations. 22 operations across 17 paths, OpenAPI 3.0.4 with 81 component schemas.
    Authenticates with an API key in the XApiKey header.
  humanURL: https://docs.debitura.com/referral-partners
  baseURL: https://referral-api.debitura.com
  tags:
  - Debt Collection
  - Debt Recovery
  - FinTech
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/debitura-referral-partner-api.json
  - type: OpenAPI
    url: https://docs.debitura.com/openapi/referral-partner-api.json
  - type: Documentation
    url: https://docs.debitura.com/referral-partners
- name: Debitura Collection Partner API
  description: For collection agencies operating cases on the platform. Managed cases, bulk ingestion jobs, and the user and
    webhook surface behind them. 48 operations across 38 paths, OpenAPI 3.0.4 with 68 component schemas. Authenticates with
    an API key in the XApiKey header.
  humanURL: https://docs.debitura.com/collection-partners
  baseURL: https://collectionpartner-api.debitura.com
  tags:
  - Debt Collection
  - Debt Recovery
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/debitura-collection-partner-api.json
  - type: OpenAPI
    url: https://docs.debitura.com/openapi/collection-partner-api.json
  - type: Documentation
    url: https://docs.debitura.com/collection-partners
properties:
- type: Documentation
  url: https://docs.debitura.com
- type: APIsJSON
  url: https://docs.debitura.com/apis.json
maintainers:
- FN: Debitura
  url: https://debitura.com
  email: robin@debitura.com
x-evidence:
  source: https://docs.debitura.com/apis.json
  source_specification_version: '0.20'
  harvested: '2026-08-01'
  request: api-evangelist/api-evangelist-network#1
  probes:
  - https://docs.debitura.com/apis.json -> HTTP 200 (2026-08-01)
  - https://docs.debitura.com/openapi/customer-api.json -> HTTP 200, 44 paths / 53 ops / 81 schemas
  - https://docs.debitura.com/openapi/referral-partner-api.json -> HTTP 200, 17 paths / 22 ops / 81 schemas
  - https://docs.debitura.com/openapi/collection-partner-api.json -> HTTP 200, 38 paths / 48 ops / 68 schemas
  note: Built from the provider's own published APIs.json. Every API, documentation URL, OpenAPI URL and the signup link come
    from that document; operation, path and schema counts were measured from the fetched specs. Pricing, plans and rate limits
    are not asserted — nothing published was found to support them, so they are left for the enrichment pipeline rather than
    guessed.
x-refine-exempt:
  reason: NOT split one-per-tag. Debitura ships three APIs on three different hosts that share tag names (Cases, Webhooks,
    Me, Users, Coverage). refine-openapis merges a shared tag across source specs into one document, which collapses the three
    hosts into whichever server it processed last — the merged Cases document carried 31 operations from all three APIs under
    a single collectionpartner-api server, so two thirds of them pointed at a host that does not serve them. The specs are
    registered whole, exactly as Debitura publishes them, until the splitter can carry per-operation servers. See api-evangelist/roadmap#6.