The LBIN API for firms and software vendors
Published on 10 October 2026 · Updated on 10 October 2026
In short
The LBIN API is the interface that lets a firm or software vendor connect its own tools to LBIN, the SaaS operating system for professionals handling company formation and compliance. It reads and feeds client files, people, documents, steps and deadlines without re-entry. Access is granted on request.
What the API is for
- Create a file in LBIN from your CRM or your client onboarding form
- Synchronise the details of shareholders, managers and beneficial owners
- Upload and retrieve documents linked to a file
- Track the progress of steps and feed your dashboards
- Receive notifications when a step changes status or a deadline approaches
The resources, described in general terms
| Resource | Typical operations | Use |
|---|---|---|
| Files | Create, read, update, list | A company being formed or monitored, with its legal form and status |
| People | Create, read, update | Shareholders, managers and beneficial owners linked to a file |
| Documents | Upload, read, list | KYC documents, draft documents, deeds and supporting evidence |
| Steps | Read, update a status | Notary, LBR, RBE, authorisation, VAT, CCSS |
| Deadlines | Read, list | Compliance calendar of each company |
| Events | Notification subscription | Status change, document received, deadline approaching |
The exact list of resources, fields and formats is provided in the technical documentation supplied with access.
Security
The API is designed according to the following principles. The detail of the mechanisms is set out in the technical documentation.
- Authentication: access through credentials specific to each integration, revocable at any time.
- Encryption: exchanges take place only over encrypted connections.
- Limited rights: each integration accesses only the resources and files it is authorised for.
- Traceability: operations carried out through the API appear in the LBIN audit trail, like those of a user.
- Personal data: the API carries KYC data; its processing must remain GDPR-compliant on both sides of the integration.
Getting access
- 1
Request
Describe your firm or your software and the integration need from the contact page.
You - 2
Technical discussion
Validation of the use case, the resources required and the rights to grant.
You and the LBIN team - 3
Test environment
Access to the documentation and to a test environment with no real data.
LBIN team - 4
Go live
Production credentials are issued once the integration is validated.
LBIN team
Access on request only
No API key or address is published on this site. The technical documentation and credentials are issued individually, after the request is validated. Never share your credentials by unsecured email or in a code repository.
Next step
Connect LBIN to your tools
Describe your integration need. We come back to you with the available resources and the conditions of access.
Frequently asked questions
Who can get access to the LBIN API?
Professionals who use LBIN, and software vendors who want to offer an integration to those professionals. Each request is reviewed to check the use case, the data involved and the rights required before access is opened. Requests are made from the contact page.
Where can I find the API documentation?
The technical documentation is not public. It is supplied with access to the test environment, once the request is validated. It describes the resources, fields, exchange formats, authentication rules and available notifications, as well as the security practices to follow.
Can the API file directly with the RCS or the RBE?
No. The LBIN API exchanges data with LBIN, not with the public registers. Filings with the Luxembourg Business Registers remain made by authorised persons, following the registers’ procedures. LBIN is designed to track the status of these steps and keep a record of them.
Can the API be tested without real data?
Yes, that is the purpose of the test environment provided before go live. It lets you build and validate the integration without handling clients’ personal data. Production credentials are issued only once the integration is validated on both sides.