Build on SolaBill API
Integrate invoice and credit note submission, monitor processing lifecycle, and automate ERP sync with secure multi-tenant client APIs and webhook events.
Documentation Map
Getting Started
Step-by-step onboarding from authentication to first invoice submission.
API Reference
Endpoint catalog, schemas, request/response examples, and status codes.
Webhooks
Event payloads, signature verification, retry model, and consumer guidance.
Sandbox
Integration-safe environment for testing happy and failure paths before go-live.
SDKs
Language clients and quick-start snippets for PHP, Node.js, and Python.
Changelog
Release notes, versioning changes, and compatibility guidance.
Integration Flow
| Step | Action | Output |
|---|---|---|
| 1 | Login via POST /api/v1/client/auth/login | Bearer access token |
| 2 | Submit invoice/credit note payload | Created document + tracking id |
| 3 | Monitor with message status endpoint | Current processing state |
| 4 | Handle webhook callback events | Near-real-time state transitions |
| 5 | Retry failed items with corrected data | Recovered delivery pipeline |
Auth Basics
Every request must include an active client token and stay within authorized tenant/client boundaries. Unauthorized or cross-tenant access attempts are denied.
| Area | Rule | Priority |
|---|---|---|
| Token Usage | Include Authorization: Bearer <token> in each protected endpoint call. | Critical |
| Scope Control | Never reuse tokens across client accounts or tenants. | Critical |
| Rotation | Rotate credentials periodically and revoke compromised tokens immediately. | High |
Integration Best Practices
- Use idempotent keys or unique business document identifiers when implementing retries.
- Validate payloads client-side before submission to reduce 422 response loops.
- Implement exponential backoff on transient errors like 429, 500, and 503.
- Persist webhook events and handle duplicates safely.
- Run regression tests in sandbox before promoting integration changes.