Integrations
One integration, whatever your stack.
There is no Sobtra SDK to adopt and no framework plugin to install. The integration surface is HTTP: a REST API at api.sobtra.com for writes and reads, webhooks for state changes. That keeps you free to integrate from any language or runtime.
REST API
api.sobtra.com/v1
JSON over HTTPS at api.sobtra.com with bearer keys scoped to a merchant and environment. Resources cover products, plans, prices, customers, subscriptions, invoices, payments, usage, add-ons and coupons.
API overviewWebhooks
Signed with HMAC-SHA256
Events for subscription, invoice and payment state changes, delivered to endpoints you register. Each endpoint holds a signing secret that can be rotated.
Webhook guideMerchant dashboard
app.sobtra.com
The same records rendered for humans: subscriptions with their periods, invoices with line items, usage per meter and permission-scoped team access.
DocumentationPayment gateways
13 providers modelled
Connect Paystack, Flutterwave, Stripe, Monnify, Nomba, PayPal, Fincra, Hubtel and others, and keep one subscription model across them.
Provider coverageWhat you actually write
Calls you would expect, and nothing invented.
Create a subscription when a customer starts paying, send usage as it happens, and handle webhooks to react to state. The example below is the shape the API uses.
curl -X POST https://api.sobtra.com/merchants/mm_8fk2/subscriptions \
-H "Authorization: Bearer sk_test_..." \
-H "Content-Type: application/json" \
-d '{
"customerId": "cus_8fk2m",
"planId": "plan_growth",
"priceId": "price_monthly_ngn",
"trialDays": 14
}'Replace the key with a test key from your merchant workspace. Test and live keys are never interchangeable.
Languages
Any runtime with an HTTP client: Node, Python, Go, PHP, Ruby, .NET, Java, or an edge worker. No package required.
SDKs
No official SDK is published yet. The docs show raw requests and a webhook verification snippet in Node so you can implement signing anywhere.
Frontends
Checkout sessions are created server-side and returned as a URL, so the browser never holds a merchant API key.
Existing billing
Sobtra can run alongside an existing provider subscription flow during migration; subscriptions are created explicitly rather than mirrored automatically.
Integration paths
Where teams usually start.
Most integrations follow the same order. Doing it in this sequence means you can see a full billing cycle before writing application code.
01
Create a product and plan
Model what you sell, then add a price in the currency you bill in.
02
Connect a provider
Add a gateway in test mode and confirm a checkout completes end to end.
03
Create a test subscription
Run a trial and a renewal in the test environment before touching live data.
04
Subscribe to webhooks
React to invoice and payment events instead of polling for state.
Start with a test key.
The quickstart walks from an empty account to a first subscription, including how to run a renewal without waiting a month.