Welcome to the Horus Software API
Read and write accounting data in Horus Office from your own application.
The Horus Software API lets your application read and update the data of a Horus Office database: accounting folders, customers and suppliers, chart of accounts, book entries, invoices, documents and more.
It is designed for software vendors and integrators who want to connect their product to the accounting records that fiduciaries and SMBs manage in Horus Office.
What you can build
- Invoicing, e-commerce or expense tools that push sales and purchase invoices, with their PDF, straight into the accounting.
- Document collection flows that send PDFs, images, XML, CODA or SODA files to be processed automatically into book entries.
- CRM or ERP synchronisation of customers and suppliers.
- Reporting, dashboards and credit control based on ledgers, balances and outstanding items.
- Payment reconciliation by matching payments with open invoices.
The API at a glance
| Protocol | HTTPS, JSON-RPC style methods such as companies.list or invoices.sales.new |
| Data format | JSON (requests and responses), multipart/form-data for file uploads |
| Authentication | OAuth 2 authorization code flow, Bearer access tokens valid for 1 hour |
| Base URL | Different for each license, obtained during authorization as api_url |
| Identifiers | GUIDs, plus human-readable search keys for accounts, daybooks, companies… |
One license, one API URLEach fiduciary or SMB using Horus Office has its own database and its own API endpoint. Your integration discovers it during the authorization flow and must never hard-code it. The Authentication overview explains how it works.
Where to start
- Register your integration to get your credentials.
- Follow the Quickstart to connect a license and make your first calls.
- Read the Core Concepts and the data model before building your integration.
How this documentation is organised
| Section | Content |
|---|---|
| Getting Started | Registration and a step-by-step first connection. |
| Authentication | The OAuth 2 flow, the license-specific API URL and the token lifecycle. |
| Core Concepts | Request and response conventions, errors, sideloading and the Horus data model. |
| Working with Accounting Data | Task-oriented guides: reading data, managing companies, posting invoices and operations, documents, matching. |
| Tools & Resources | Testing with the API Reference and Postman, versioning policy and support. |
The API Reference tab documents every endpoint with its parameters, schemas and examples.
Need help?
Write to [email protected]. See Support & FAQ for what to include in your message.
Updated about 1 hour ago