My Products
Help
Dante Cavallin
CONTRIBUTOR *

https://integration.visma.net/API/service/ seems to be down ??

by Dante Cavallin

Hi I am trying out the new Visma Connect Authentication and I have created a new test application and as I understand I should use the base URI : https://integration.visma.net/API/service/ instead of https://integration.visma.net/API/ as I have been doing  before when using VNI.

 

When I try to access enpoints using this new base uri I get the following:

503 Service Temporarily Unavailable

Is this not live yet or what ?

 

 

4 REPLIES 4
Dante Cavallin
CONTRIBUTOR *

by Dante Cavallin

Hi, it is not the generating of a token I have a problem with it is the url to use with the new token ?

The old base URI does not work :https://integration.visma.net/API/ when I try to call enpoints on this uri I get an error if I don't include ipp-company-id and ipp-application-type headers.

So my question is really what base uri am I going to use ?

Accepted solution
Yıldırım
VISMA

Hello Dante, 

to correct the information I've shared, the base URL will still be the same, but the request headers should be set as shown below. (Visma Connect Token stores the Company details)

curl -X 'GET' \
  'https://integration.visma.net/API/controller/api/v1/account' \
  -H 'accept: application/json' \
  -H 'authorization: Bearer xxxxxxxxxxxxxxxxx'

 

Dante Cavallin
CONTRIBUTOR *

Hi just a question, how long does it take to get a new application approved in the developer portal, I added a new application about 3 weeks ago but it still says 'pending' ?

 

Yıldırım
VISMA

by Yıldırım

Hi,

after following the steps explained in the documentation, token can be generated with the specified schema. 
Getting started with Visma Developer Portal

see: 4.3 Generating a new API Token

-----------------------------------------------------------------------------------------------------

URL: POST > https://connect.visma.com/connect/token
1) Request Headers
Content-Type : application/x-www-form-urlencoded
2) Request Body
a) client_id : ClientID (Generated in Developer Portal)
b) client_secret : ClientSecret (Generated in Developer Portal)
c) grant_type : client_credentials
d) scope :  application scope (can be seen in the developer portal)
(Depending on what scopes have been allowed by the tenant
administrator in the Visma App Store for your application.)
-----------------------------------------------------------------------------------------------------