# Receeve

**Canonical:** https://apis.io/providers/receeve/  
**Website:** https://api.receeve.com/  
**APIs profiled:** 14

Receeve is a no-code debt collection and receivables management SaaS platform, founded in Hamburg, Germany and backed by Speedinvest. It was acquired by InDebted and now operates as the "Receive" product — a debt servicing platform that lets creditors, banks, lenders, utilities and collection agencies automate the full collections lifecycle: importing accounts and claims, running configurable dunning strategies and journeys, sending multi-channel communications (email, SMS, letters, calls), generating hosted debtor landing pages, and reconciling payments, promises-to-pay, instalment plans and settlements. The Receive Client API is an OpenAPI 3.0 REST API secured with OAuth2 client-credentials (Bearer tokens) and emits an extensive catalog of signed webhooks for account, claim, communication, finance, landing-page and strategy events.

## Kin Score — 35.3 / 100 (thin)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 35.3).

| Facet | Score |
|---|---|
| Discoverability | 81.5 |
| Contract Quality | 62.8 |
| Governance | 16.7 |
| Contract Governance | 16.7 |
| Operational Transparency | 7.9 |
| Developer Ergonomics | 32.7 |
| Commercial Clarity | 7.9 |
| Access Clarity | 7.9 |

Regulatory layer — **Payments**: 34.4 (matched via tags).

## Agent readiness — 41.7 (agent-ready)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | derived |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | yes |
| Idempotency | documented |
| Error Semantics | documented |
| OpenAPI Examples | verified |
| Rate Limit Signal | no |
| Event Surface Described | derived |
| Agent Skills | derived |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Self-serve signup — onboarding: self-serve, pricing: unknown, trial: no (confidence: medium).

## APIs (14)

- **Receeve Account API** — A formal business arrangement providing for regular dealings or services (such as banking, advertising, or store credit) and involving the establishment and maintenance of an ac...
- **Receeve AccountMandate API** — The AccountMandate API from Receeve — 3 operation(s) for accountmandate.
- **Receeve Claim API** — A claim is an outstanding payment that is owed. You can always update this balance if multiple payments are missed and you want to aggregate the amounts.
- **Receeve CustomTriggers API** — The CustomTriggers API from Receeve — 1 operation(s) for customtriggers.
- **Receeve Debtor API** — The Debtor API from Receeve — 1 operation(s) for debtor.
- **Receeve Event API** — Event that happened in Receive systems, for example, claim created or email delivered.
- **Receeve Files API** — The Files API from Receeve — 1 operation(s) for files.
- **Receeve Finance Instalments V2 API** — The Finance Instalments V2 API from Receeve — 5 operation(s) for finance instalments v2.
- **Receeve Finance Settlements API** — The Finance Settlements API from Receeve — 5 operation(s) for finance settlements.
- **Receeve Journey API** — This is the overall strategy to resolve the outstanding payment or debt.
- **Receeve LandingPage API** — The Landing Page of the Debtor, used to display, pay the Claims (or other use cases).
- **Receeve Message API** — Communication message in .eml format that was sent to Debtor.
- **Receeve PromiseToPay API** — The PromiseToPay API from Receeve — 1 operation(s) for promisetopay.
- **Receeve Security API** — The Security API from Receeve — 1 operation(s) for security.

## MCP servers (1)

- **Receeve MCP Server**

## Agentic access (1)

- **Receeve Agentic Access** — 46 operations · 34 acting · 2 human-in-the-loop

## Security (2)

- **Receeve Authentication** — oauth2/apiKey · 2 schemes
- **Receeve Domain Security** — TLSv1.3 · DMARC

## Tags

Company, Debt Collection, Receivables Management, Debt Servicing, Collection, Fintech, Payments, Webhook, Financial-Services, Dunning

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/receeve/). Scores are computed from the provider's own public artifacts under a published rubric.