Robaws API
We distinguish two types of integrations: a custom integration and a marketplace integration.
- A custom integration is built for one specific customer to support a customer-specific process.
- A marketplace integration is a standard integration that is made available to all Robaws customers in the Robaws integration marketplace.
The difference between the two lies in the authentication method. The requirements for a marketplace integration are slightly stricter.
I want to build a custom integration
For custom integrations, HTTP Basic Authentication is the recommended authentication method. We recommend you to create a separate user in the customers' Robaws environment. If you check the box 'API only', the user is free of charge. It is considered a best practice to create a separate role for that user, granting only access to the modules needed by the integration.
Getting started
- Test tenants can be provided free of charge for 14 days. If needed this period can be extended.
- Contact us on billing@robaws.be to get started.
I want to build a marketplace integration
For marketplace integrations, the OAuth2 Authorization Code flow is the required authentication method. The requirements are:
- You do not refresh access tokens until they are (almost) expired.
- You build the integration against a Robaws test tenant first.
- In order for your integration to become available for production (in the Robaws marketplace), a demo video will be required where you demonstrate the integration.
- You'll need to provide us with an URL to the page where the customer can initiate the OAuth2 flow at your side.
- Polling is discouraged! If your integration should be aware of a change that happened, you should use the webhooks.
Getting started
- For a marketplace integration, you'll need an OAuth2 client ID & client secret.
- Contact us on support@robaws.be to get started.
Reference documentation
https://app.robaws.com/public/api-docs/robaws
Your API integration should take into account the Robaws rate limiting response headers. HTTP 429 errors will be monitored. If they occur too often, Robaws team will intervene to temporarily block the integration until you provide a solution. More details about the rate limiting can be found in the reference documentation.
Updates
See the API changelog
Specific topics
API filtering, paging & sorting
Updating information (PUT vs PATCH)
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?
Bijgewerkt op: 28/11/2025
Dankuwel!