• Robaws API

  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. Updates See tPopulair

• Webhooks

  Navigate quickly to: Using webhooks Verifying the signature Some considerations Supported event types Using webhooks To start using webhooks with Robaws, register your webhook endpoint by doing a POST on /api/v2/webhook-endpoints. For the full request definition see the api reference docs. Please do store thEnkele lezers

• API filtering, paging & sorting

  Filtering on standard fields Each root entity collection resource contains some specific filter parameters. If you have extra filtering needs that could improve the performance of your API usage, please let us know on support@robaws.be and we will evaluate your request. Filtering on extra fields Filtering on extra fields is possible by using the following URL syntax. Be aware that the and the characters must be URL encoded! Text, Link, Multiple choice fields GET /api/v2/artEnkele lezers

• API rate limiting

  Robaws API requests are subject to rate limiting. At the moment, we use the token bucket algorithm with a replenish rate of 15 and a burst capacity of 20. That means you can do at least 15 requests per second. As a consumer of our API, you should make your client software aware of this rate limit. You can do this by looking at the x-ratelimit-remaining response header and pausing api calls for a second when the remaining becomes close to zero. When you receive a 429 Too Many Requests error,Weinig lezers

• Updating information (PUT vs PATCH)

  When in doubt, always prefer PATCH to PUT! There are 3 endpoints per resource which you can use to perform updates. The first one is PUT, which completely replaces the entity with the provided payload. This is not handy for big entities with many properties. Therefore we provide two variants of the PATCH method: Json Patch and Json Merge Patch. Json Merge Patch is the most trivial because it allows you to only define the properties that you want to update. Json Patch is different but moWeinig lezers

• API changelog

  2024-04-03 Added possibility to start the approval request for a purchase invoice. 2024-02-08 Added possibility to add or update the document of a purchase invoice New field 'documentId' is added to the purchase invoice api model. In order to obtain a document id for your file, please follow the steps as described in Uploading files. AddedWeinig lezers