Visma.Net API Swagger page not showing

[olesko]

Hi,

The Swagger API page seems to be not functional.

Oleg

[guidol]

test whether can post again.

[guidol]

Apologies for the test. My privileges on the forums seem to be flip flopping, leading to disappearing posts/replies. I have created a separate topic on the problems with Swagger, since this one has been marked already as solved.

[guidol]

The Swagger seems seriously broken, and this may explain the intermittent errors across a larger user base of Visma.net users on Invantive Cloud. The impact depends on whether the users have already switched to the new Swagger released with 9.33 (no release date in Swagger).

Issue 1: the Swagger metadata page https://integration.visma.net/API-index/doc/swagger seems to open, but the content is seriously changed with major impact for all users that we support since the datamodel is generated dynamically.

We are missing for instance:

- ipp-company-id
- ipp-application-type

The first one is critical for many users, since we don't know how to exchange the company and discover that an API has different outcome per company (we call it "partitions" in the SQL engine)

The removal of ipp-company-id may explain the still occurring Bad Requests (see forums post https://community.visma.com/t5/Forum-in-Developers-Visma-net/HTTP-400-Bad-Request-answers/td-p/55807...), such as in an error like:

Invalid parameter exception: ipp-company-id (12002_12002_7b28d6d8-104b-4acc-991b-e5290bde8fdb)

Question: where can we find current documentation for providing the company ID? We seem unable to find the docs.

Issue 2. The Swagger-UI seems unstable. The Swagger-UI page https://integration.visma.net/API-index/ opens on my Chrome on Windows.

However, it gives a 404 on service-worker.js:

A bad HTTP response code (404) was received when fetching the script.
main.17349a4d.js:2 Error during service worker registration: TypeError: Failed to register a ServiceWorker for scope ('https://integration.visma.net/API-index/') with script ('https://integration.visma.net/API-index/service-worker.js'): A bad HTTP response code (404) was received when fetching the script.

At a co-worker on Chrome on Windows on another PC, the name of the main...js download changes on every Hard Refresh (Ctrl+F5), see picture. The browser shows an empty page.

Question: none, we can live without Swagger-UI, as long as the actual metadata is correct.

Issue 3: Authorize does not work at my PC. It can authorize after selecting all scopes (selecting none gives a weird error), but the following page is displayed:

However, I can access Visma.net without problems:

I was also able to complete the full Visma.net authorization flow using Code Grant Flow on Invantive Cloud for Visma.net Financials. However, an old database with a previously completed Code Grant Flow would not open and spin forever in a loop with Visma.net API servers.

Question: none.

Issue 4: I seem unable to find any hints on these changes in the release notes on https://community.visma.com/t5/News-in-Developers-Visma-net/Release-Notes-Visma-Net-API-9-32-0-02-02.... The financial periods is known; it was an issue for one of our older Visma.net users.

Question: where can we find current documentation of the changes?

[Stefan Hult]

Any news on the non-functioning Swagger?
/Stefan

[Magnus Johnsen · Accepted solution]

Hi,

Could you please clear your cookies and try again?

Thank you.

[olesko]

Additional info: It doesn't work on my MacBook, not in Chrome nor in Safari. Calling it from Postman gives the following error:

You need to enable JavaScript to run this app

JavaScript is enabled in my Chrome.