No access

Step 6. Making the step to production

  1. Accounts:

    Creating accounts for the Visma Developer Portal for production can be done in two ways. We recommend always using two Visma Developer Accounts, although that's a bit more complicated.

    1. If you are sure that your application will only be used for 1 Brincr account, you can have the same Visma Developer Account for the application and the link to Brincr.
    2. The recommended way is using two Visma Developer Portal Accounts. One for the application itself and one for the link with the Brincr account. The advantage to this, is that it's possible to add multiple Brincr accounts to the same application. The Visma Developer Portal application account should be run by a developer, while the Visma Developer Portal account linked to a Brincr account, should be run by the same person that manages the Brincr account. If you want to set this up, please read our FAQ, question "I hired a developer for developing my application. Do I need to do all the steps?".

  2. Requirements:

    Because data integrity is very important on production, moving to production involves validation of your integration on sandbox. Before requesting validation, you should meet the following requirements:

    1. Sandbox should be running without errors
    2. Sandbox should be running without unnecessary requests
    3. Only validated scopes will be approved
    4. You have requested the scopes in the Visma Developer Portal

    5. Do a test-run on sandbox

      1. You have created a test-run of all the requests you are doing on sandbox.
      2. For this, you need to remove all cache and run the application exactly two times.
      3. Make sure there are no other requests done the day of the test-run.

  3. Requesting sandbox validation:

    If you meet all requirements, fill out this form to request validation:

  4. Activating production integration:

    Once your request is approved, setting up the authentication for production is almost the same as on sandbox. There are some differences:

    1. Read production instead of sandbox
    2. In 1.1.1, use app.brincr.com/register as a link (for new Brincr users)
    3. In 1.2, append (production) to your application name
    4. In 4, use https://connect.visma.com/connect/token as the url
    5. In 5, use https://api.brincr.com/api/v1/categories as the url
    6. The Brincr user needs to do steps 1 and 3.2.3
    7. The developer needs to do steps 2 through 3.2.2

  5. Requesting production activation:

    If you meet all requirements, fill out this form to request production activation. Our team will approve your request asap. Once approved your integration works on production data.

  6. Finalize:

    Once your API integration works on the production environment please check on regular base:

    1. the amount API calls on production environment by API Statistics
    2. the amount of errors in API calls on production environment by API Statistics
    3. new updates on https://api-docs.brincr.com/changelog
Previous step
Calling the Brincr API