API general information

Authentication best practices

Our API's are secured using HTTP basic authentication. It is considered best practice to create a user per service/client/third party using the API. This extra users are free of charge and it prevents API connections from being broken due to password changes. It is also recommended to create a specific user role for those users granting only access to the necessary modules.

API v2 reference documentation

New integrations should always use API v2. If there are missing fields/resources, please contact us on support@robaws.be and we will evaluate your request.


Example use cases
Creating a work order
Synchronizing article data with your own database
Creating a client/lead from a website form
How to fetch invoices for import into accountancy software?

API v1 reference documentation


Warning! API v1 will retire in some time. A specific date for this retirement is not yet confirmed. It is recommended that you do not implement API v1 anymore and that you consider moving tot API v2 as soon as possible. If you have use cases that are now supported in API v1 but not yet in API v2 please let us know on support@robaws.be.

Backwards compatibility on API v1 resources is not guaranteed.

Why is API v1 retiring?

The design of API v1 does not allow us (Robaws) to ensure backwards compatibility while providing many updates on the software. It also is not flexible enough to support enough use cases. It is the idea that API v2 will have an 'infinite' lifespan and will always be kept backwards compatible.
Was dit artikel nuttig?