REST and JSON
Work with documented HTTP endpoints, JSON requests and standard response conventions.
API
Build on Clientlly
Review the integration documentation, then contact us to confirm API availability for your plan.
# Every request carries a token and stays inside one organisation
GET /api/invoices
Authorization: Bearer <access-token>
Accept: application/json
# Results follow the caller’s role and module permissionsDeveloper portal
What the developer portal covers
Plan a secure integration before requesting access for your organisation and subscription plan.
Authentication and permissions
Use Bearer access tokens and respect the roles and module permissions assigned in Clientlly.
Organisation-scoped records
Keep requests within the active organisation and the records the authenticated user is allowed to access.
Connected business areas
Build approved workflows around customers, products, invoices, payments, inventory, organisations and reports.
Errors and safe handling
Understand response codes, validate input and keep tokens out of browser code, mobile binaries and public repositories.
Access and implementation support
Review the public reference, then contact Clientlly to confirm approved operations and availability for your plan.
Getting access
From reference to production in three steps
- 01
Read the reference
Browse endpoints, request formats and error codes in the public developer documentation.
developers.clientlly.com - 02
Confirm access
Contact Clientlly to confirm approved operations and API availability for your plan.
/contact - 03
Build server-side
Issue a token for a user with the right role and keep it on your server — never in the browser or an app binary.
Authorization: Bearer
Keep access tokens private
Tokens act with the permissions of the user they belong to. Keep them out of browser code, mobile binaries and public repositories.
Bring your business workflows together
Start a 14-day free trial — no card, no lock-in. Import your customers and invoices and see the full picture on day one.