Home · Provider docs
Provider docs
Provider docs
Integrate Florentin into your backend — via REST, SDK or MCP. One REST API per domain, bearer token, JSON as { data, meta }.
One API, bound to your domain
The provider API is the server side of Florentin: with it you create customers, define products and plans, record usage, issue keys and react to events. It's organised as one REST API per provider domain and authenticated with a bearer token bound to exactly that domain.
Successful responses come as { data, meta }, errors as { error } with the matching HTTP status. Alternatively, you build with your coding agent via the MCP, without learning the endpoints one by one.
Basics
How the provider API works
✓
Base URLhttps://<provider-subdomain>.florentin.ai/api/v1
✓
AuthAuthorization: Bearer 42|<secret>
✓
FormatJSON, responses as { data, meta }.
✓
MCPOAuth via /api/mcp — build with your agent.
Example
Create a customer
curl -X POST https://acme.florentin.ai/api/v1/customers \
-H "Authorization: Bearer 42|kP3f9c…" \
-H "Content-Type: application/json" \
-d '{ "name": "Ada Lovelace", "email": "team@kunde.io" }'
← 201 { "data": { "id": "7b9c3e2a-…", "email": "team@kunde.io" },
"meta": { "message": "Customer created successfully" } }Documentation
All chapters
01Getting startedFirst call in minutes.↗02AuthenticationBearer tokens & scopes.↗03Products & endpointsMake what you sell billable.↗04CustomersCreate, manage, bill.↗05BillingPlans, subscriptions, invoices.↗06WebhooksReceive signed events.↗07Errors & paginationAPI conventions.↗08API reference (Scalar)All endpoints & schemas.↗09MCP serverBuild with your agent (OAuth).→
FAQ
Frequently asked
How is the base URL structured?
Per provider domain: https://<provider-subdomain>.florentin.ai/api/v1 — or your own custom domain.
Which languages are supported?
Generated clients for cURL, TypeScript and Python are in the Scalar reference.
Build your product. We'll handle the rest.
Accounts, billing, credits, portal, access — integrated. Stripe fully included.
Start free →