Debitura is a B2B cross-border debt collection platform, API-first, with consumer claims taken on only as larger portfolios. Pricing is No Cure, No Pay: a success fee only when money is recovered, from 6% in Europe and 7.5% elsewhere. 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 API contracts indexed 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.
The Debitura catalog on APIs.io includes 1 Spectral governance ruleset.
Debitura’s developer surface includes pricing, documentation, engineering blog, and 2 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Payments regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/debitura/"><img src="https://apis.io/badge/debitura/card.svg" alt="Debitura on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Rate-Limit Signaling+7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented) Ask about this →
Delegated User Identity+6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →
8 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
For platforms embedding debt collection as a referral: refer and preview cases, manage referred clients, mint OAuth tokens, and report on referrals, with webhooks.
name: Debitura
description: 'Debitura is a B2B cross-border debt collection platform, API-first, with consumer claims taken on only as larger
portfolios. Pricing is No Cure, No Pay: a success fee only when money is recovered, from 6% in Europe and 7.5% elsewhere.
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://artifacts.apis.io/debitura/apis.yml
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: high
source:
- openapi
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
source: []
generated: '2026-11-13'
method: derived
created: '2026-08-01'
modified: '2026-10-06'
specificationVersion: '0.23'
tags:
- Debt Collection
- Accounts Receivable
- Debt Recovery
- Fintech
- Payments
- Invoicing
- Webhook
tags_raw:
- Debt Collection
- Accounts Receivable
- Debt Recovery
- FinTech
- Payments
- Invoicing
- Webhooks
apis:
- aid: debitura:debitura-customer-api
name: Debitura Customer API
description: 'For creditors: upload invoices to collection and track cases, with contracts, divisions, coverage, payments,
tasks, users and webhooks.'
humanURL: https://docs.debitura.com/clients
baseURL: https://customer-api.debitura.com
tags:
- Cases
- Contracts
- Coverage
- Divisions
- Me
- Payments
- Task
- Test Cases
- TestWebhooks
- User
- Webhook Events
- Webhook
tags_raw:
- Cases
- Contracts
- Coverage
- Divisions
- Me
- Payments
- Tasks
- TestCases
- TestWebhooks
- Users
- WebhookEvents
- Webhooks
properties:
- type: OpenAPI
url: openapi/debitura-customer-api-openapi.yml
- type: Documentation
url: https://docs.debitura.com/clients
- type: SignUp
url: https://app.debitura.com/CreditorApiKey
- aid: debitura:debitura-referral-partner-api
name: Debitura Referral Partner API
description: 'For platforms embedding debt collection as a referral: refer and preview cases, manage referred clients, mint
OAuth tokens, and report on referrals, with webhooks.'
humanURL: https://docs.debitura.com/referral-partners
baseURL: https://referral-api.debitura.com
tags:
- Cases
- Clients
- Coverage
- FilterOptions
- OAuth
- PreviewCases
- ReferralPartners
- Reporting
- Webhook
tags_raw:
- Cases
- Clients
- Coverage
- FilterOptions
- OAuth
- PreviewCases
- ReferralPartners
- Reporting
- Webhooks
properties:
- type: OpenAPI
url: openapi/debitura-referral-partner-api-openapi.yml
- type: Documentation
url: https://docs.debitura.com/referral-partners
- aid: debitura:debitura-collection-partner-api
name: Debitura Collection Partner API
description: 'For collection agencies operating cases on the Debitura platform: work managed cases, run ingestion jobs,
and manage users and webhooks.'
humanURL: https://docs.debitura.com/collection-partners
baseURL: https://collectionpartner-api.debitura.com
tags:
- Cases
- IngestionJobs
- ManagedCases
- Me
- Test Cases
- TestWebhooks
- User
- Webhook Events
- Webhook
tags_raw:
- Cases
- IngestionJobs
- ManagedCases
- Me
- TestCases
- TestWebhooks
- Users
- WebhookEvents
- Webhooks
properties:
- type: OpenAPI
url: openapi/debitura-collection-partner-api-openapi.yml
- 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.
common:
- type: Pricing
url: https://www.debitura.com/pricing
name: Debitura Pricing (No Cure, No Pay success fee)
- type: Documentation
url: https://docs.debitura.com/
- url: https://www.debitura.com/blog
type: Blog
- type: CapabilityMap
url: capabilities/debitura-capability-edges.yml
name: Debitura Business Capability Map
- type: Website
url: https://debitura.com
Debitura API — frequently asked questions
Does Debitura have an API?
Yes. APIs.io lists 3 APIs from Debitura, including Debitura Customer API, Debitura Referral Partner API and Debitura Collection Partner API.
Is there an OpenAPI specification for the Debitura API?
Yes. APIs.io indexes 3 OpenAPI specifications for Debitura, each linked for download from this page.
How do I authenticate with the Debitura API?
Debitura uses bearer-token authentication.
Does Debitura have an MCP server?
Yes. APIs.io lists 1 MCP server for Debitura: Remote MCP server at mcp.debitura.com over HTTP; 16 tools listed.
Is the Debitura API ready for AI agents?
Debitura has a Kin Score of 24.1 out of 100 (emerging) and an Agent Readiness score of 40.5 (agent-native), scored by API Evangelist on 2026-11-13.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.