Stable Pro API · v1
Stable Pro API
Read the economic facts of a stable — charges, adjustments, payments, credits, receipts — to issue invoices in your own software.
Stable Pro is the management software of riding stables. It keeps the economic facts of each stable: what every customer owes (charges), every correction to it (adjustments), the money received and refunded (payments), customers' credit, and Stable Pro receipts.
The API lets invoicing and accounting software read those facts and issue its own documents: invoices, credit notes, tax reports. Stable Pro never issues tax documents; your software does. One contract for every software and every country: there is no module for a specific program, and no country-specific field.
What you can build
- Invoicing: read a charge, issue the invoice; read an adjustment, issue a credit note; read a payment, mark the invoice paid.
- Synchronisation: read the event log (
GET /events) from your saved cursor and process what changed since last time. - Reconciliation: read lists filtered by customer or accounting month and compare them with your books.
Quick start
- The stable owner creates a connection in Stable Pro (Settings → Connections) and gives you its key. A test key starts with
sp_test_and works on the staging environment, with test data (see Test environment). - Call the API with the key:
curl https://staging.stable-pro.com/api/v1/organization \
-H "Authorization: Bearer sp_test_…"
- Read the stable's history from the start, then keep reading from your cursor:
curl "https://staging.stable-pro.com/api/v1/events?limit=100" \
-H "Authorization: Bearer sp_test_…"
Each event points to an object (data.url): read it, process it, and save next_cursor when the page is done.
Base URLs
| Environment | Base URL | Keys |
|---|---|---|
| Production | https://app.stable-pro.com/api/v1 | sp_live_… |
| Staging, with test data | https://staging.stable-pro.com/api/v1 | sp_test_… |
Read next
- Authentication and permissions
- Conventions: amounts, dates, codes, lists and filters, languages
- Events: how to stay in sync
- Errors
- Reference: every endpoint and every field, generated from the OpenAPI contract