Hi Magnus, from what I see in the logging I suspect you are also using the erp-api-background header in the status retrieval GET request, hence the 400. Could you check? Thanks in advance!
Hello, Which GET request are you referring to? Right now we are not doing any GET requests because our workflow is dependant on the POST returning the background action id. It was working up until october 22. and we did not make any changes to our code.
I am referring to the GET request to retrieve the status. If you are not doing any GET requests that could not be it. There has not been a code change. I have tested this endpoint and it accepts all background operations without any complaints. I advice you to test this from an isolated client, like Postman, to clarify what the issue could be. If that does not help, more in depth investigation is needed. In that case I advise you to contact country specific support https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-cha...
The request worked properly in Postman. I have no idea why the same request does not work from azure logic app. I made a work around through an azure function and that works.
.gif "VISMA"){kind=icon}
Visma Denmark
Visma Finland
Visma Latvia
Visma Netherlands
Visma Norway
Visma Sweden
Visma Developers & Partners
Visma Latin America