Authentication
Authentication to Visma Net API is done through Visma Connect. Visma Connect is a multi-tenant identity provider. Tenants are organizations (businesses) that provide an API-context. A given user may have access to multiple tenants and will choose which to connect to your application upon each single sign-on flow.
You’ll need to create an application in the Visma Developer Portal, available at https://oauth.developers.visma.com, before getting started.
To learn more about this process see this document https://oauth.developers.visma.com/service-registry/documentation/overview. Please explore Visma Developer Portal documentation.
Endpoints
Visma Connect endpoint details:
| Endpoint | URL |
|---|---|
| Discovery | https://connect.visma.com/.well-known/openid-configuration |
| Authorization | https://connect.visma.com/connect/authorize |
| Token | https://connect.visma.com/connect/token |
| Userinfo | https://connect.visma.com/connect/userinfo |
| Endsession | https://connect.visma.com/connect/endsession |
Visma Connect Token
Your application requests specific permission scopes and is granted an access token upon a user’s approval.
There are two scenarios that are supported by Visma Connect:
- Interactive authentication of users, that must provide their credentials in a login form. That requires the authentication flow to use the Authorization Code or Authorization Code with PKCE grant type.
- Authentication of a service, using a client ID and a client secret. That requires the authentication flow to use the Client credentials grant type.
Once the authentication process has completed successfully, you can make API calls by providing the valid access token with each API request using the authorization header.