Frequently Asked Questions (FAQ)
Here, we've compiled answers to some of the most common questions about our API. If you don't see your question answered, feel free to reach out to our support team at api@brincr.com (mon-fri 0900-1200) for further assistance. In time, we will extend this page on regular base.
Although the entire documentation is in English, we also speak Dutch.
You can reach our API team only by email. Please contact our API team at api@brincr.com (mon-fri 0900-1200). We try to answer your question as soon as possible. For urgent matters, please add URGENT to the subject.
Default limit is 60 per minute per connection. If you go over the limit, you'll get an 429 error.
If you need more requests, please contact our Sales team: sales@brincr.com or +31 (0)85 – 273 35 36
If you need more requests, please contact our Sales team: sales@brincr.com or +31 (0)85 – 273 35 36
Yes, development skills are mandatory. Your are going to work with valuable data of the enduser. Proper knowledge of datasecurity, coding, RESTful API development are required to create an efficient and reliable integration.
Unfortunately no. We take care of the Brincr API and Brincr application. That is our core business. We can advise you to find a development partner. Please contact our team at api@brincr.com
Unfortunately, this is not possible. We follow strict procedures to protect your (production) data from any polution. So first develop your integration on Sandbox. Once our team approved your integration by checking the usage of scopes, amount of API calls and quality of them, you can launch at production.
Ask the owner of the Brincr production account to create (anonimized) export files of production data. You can import these on your Sandbox account and create a solid dataset.
Please login in to your Sandbox account. Once logged in, fill in a COC (Chamber of Commerce / KvK) number in your company settings (Miscellaneous > Settings > Company settings).
Not at this moment. In future we launch a GIT repository with working examples.
You probably didn't create your application as a
service application. Please follow the steps in 2.1 to properly create the application.
Please use https://api-docs.brincr.com to test your values. This is only available for sandbox.
There is most likely a problem with the invitation code. Please follow the steps in 3.2.2 and 3.2.3.
For Sandbox:
- We recommend the developer to do all the steps on sandbox. That way, he also has access to the API statistics page on sandbox (Miscellaneous > Settings > Api Statistics).
For Production:
- You need to do all the steps in the Brincr Application, and use the
invitation codein Visma Developer Portal. (1, 2.1.3 and 3.2.3) - The application-steps must be done by the developer. (2.1.1 to 2.1.2, 2.2 to 3.2.2)
Request the scope in the Visma Developer Portal, logged in as the application. For sandbox it's automatically approved. For production, you'll need to request validation. Only the additional scope will be verified on sandbox.
Because your contract with the Brincr user is changing, the Brincr user needs to accept the new scope.
After the scope is accepted, login in the Visma Developer Portal account that is linked to the Brincr account. For sandbox this usually is the same account.
Go to:
Don't forget to add the scope to the token request.
Because your contract with the Brincr user is changing, the Brincr user needs to accept the new scope.
After the scope is accepted, login in the Visma Developer Portal account that is linked to the Brincr account. For sandbox this usually is the same account.
Go to:
Visma App Store -> My Apps -> [Your Application] and activate the scope for this account.Don't forget to add the scope to the token request.
Not currently, but we have this feature on the roadmap.