Access token

Step 6. Making the step to production

1. Accounts

   The developer needs to make their own account on the Visma Developer Portal Production environment: see step 1.4 for a detailed explanation.
   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 managed by a developer, while the Visma Developer Portal account linked to a Brincr account, should be managed by the same person that manages the Brincr account.

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:

   Your full name

   Your email address

   Your phone number

   Company name on sandbox

   When do you plan to have production up and running?

   Anything to add?

   I meet all the requirements in step 6.2

   I will abide by the rate limit and respect the fair use policy.

   I am human.

   I promise this data is the truth.

   Submit

4. Activating production integration

   Once your request is approved, setting up the authentication for production is almost the same as on sandbox.
   All previous steps should be repeated with the following differences:

   1. References to 'sandbox' should be read as 'production'
   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 follow steps 1, 2.1.3 and 3.2.3
   7. The developer needs to follow steps 2 through 3.2.2 (except 2.1.3)

5. Requesting production activation

   If you meet all requirements and you have requested your required scopes for production, fill out this form to request production activation. Our team will approve your request as soon as possible. Once approved, your integration works on production data.

   Your full name

   Your email address

   Your phone number

   Company name on sandbox

   When do you plan to have production up and running?

   Anything to add?

   I am human.

   I will abide by the rate limit and respect the fair use policy.

   I promise this data is the truth.

   Submit

6. Finalize

   Once your API integration works on the production environment please check the following on a regular basis:

   1. the amount of API calls on the production environment, found on the API Statistics page
   2. the amount of errors in API calls on the production environment, found on the API Statistics page
   3. new updates, found on the changelog page