RCUR API · v2.0.0
Build recurring payments into your product
Build on RCUR: manage customers, subscriptions, payment links and payments from your own software.
The RCUR API is a REST API. It accepts JSON request bodies, returns JSON responses and uses standard HTTP verbs, status codes and bearer authentication.
Every request goes to the same base URL:
https://rcur.app/api/v2
Quickstart
- Create an API key on the integrations page in RCUR.
- Send it along as a bearer token, together with
Accept: application/json:
curl https://rcur.app/api/v2/organizations/me \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Accept: application/json"
- Browse the API reference for every endpoint, or read up on authentication, errors and pagination.
Always up to date
This reference is generated from the RCUR source code on every release, so what you read here is what the API does. The raw OpenAPI 3 specification is available at /openAPI.json for use in Postman, Insomnia or a client generator, and /llms.txt gives AI assistants an index of every page.
Resources
Customers
5 endpointsThe people and companies you collect payments from.
Payment Links
3 endpointsShareable links where customers pay once or sign up for a subscription.
Subscriptions
5 endpointsRecurring payments on a schedule, charged through Mollie.
Follow-ups
3 endpointsAutomatic retries and reminders for payments that failed.
Orders
2 endpointsOrders placed through payment links and subscriptions.
Payments
3 endpointsIndividual payments, including one-off charges on a mandate.
Mandates
4 endpointsPermissions to charge a customer's bank account or card.
Products
5 endpointsThe products you sell, with their price and VAT.
Organization
2 endpointsYour own RCUR account and its Mollie profiles.