to get a personalized navigation.
to get a personalized navigation.
Hi,
I'm not able to send the attachment to Visma.Net API using the endpoint:
Hi,
Usually, IPP Error 5520 is caused by network issues and will resolve itself. Please try again, and if the error persists, please contact us for further support.
Best regards
Oskar Jansson
Still the same issue:
Status 400 Bad Request. The request failed with reason Bad Request
POST to https://integration.visma.net/API/controller/api/v1/customerInvoice/020027/Attachment
-- Response body: --
{"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_988d31cb-76e4-476a-8dc5-15ae8a85a2cb","ExceptionDetails":""}
-- Request body: --
[{"Headers":[{"Key":"Content-Type","Value":["application/octet-stream"]},{"Key":"Content-Disposition","Value":["form-data; name=\"file\"; filename=\"test_file.pdf\""]}]}]
-- Response headers: --
Date: Wed, 04 Sep 2024 20:53:39 GMT
Server: Apache/2.4.52, (Debian), OpenSSL/1.1.1n
Strict-Transport-Security: max-age=31536000; includeSubDomains, max-age=31536000; includeSubDomains
ipp-request-id: 11cc675b-f762-4df4-8a43-b25889843ec5
X-Content-Type-Options: application/json
Pragma: no-cache
X-Handled-By: Visma-PX.Export/AuthenticationManagerModule
Referrer-Policy: origin-when-cross-origin
VnfInstanceId: ERP_NO_DEMO_0017
Access-Control-Expose-Headers: Request-Context
Cache-Control: no-cache
Feature-Policy: geolocation 'none'; vr 'none'; payment 'none'; midi 'none'; microphone 'none'; fullscreen 'none'; encrypted-media 'none'; camera 'none'; autoplay 'none';
X-XSS-Protection: 1;mode=block
Request-Context: appId=cid-v1:745938e4-e9a9-4ad4-b9ae-c57b6b9a0cc9
Set-Cookie: LegacyUI=0; path=/; HttpOnly,UserBranch=13; path=/; HttpOnly,Locale=TimeZone=GMTE0000U&Culture=en-GB; path=/; HttpOnly,UserDisplayName=; expires=Tue, 03-Sep-2024 20:53:37 GMT; path=/; HttpOnly
Connection: close
Transfer-Encoding: chunked
-- Request headers: --
User-Agent: iizy.no/1.252.3
Authorization: Bearer **
ipp-company-id: ***
ipp-application-type: Visma.net Financials
Accept-Charset: utf-8
Accept: application/json
Hi,
Has this been successful for you before?
Please try again today. If the issue persists, please provide us with your Client ID and Company ID or contact your local support here:
Best regards,
Oskar Jansson
Hi,
No, it never worked.
Hi,
Are you using the old VNI authentication method? If so, this could be causing the problem. Step 1 is then to migrate to Connect Authentication.
You will find information about this here: https://community.visma.com/t5/News-in-Developers-Visma-net/Urgent-Visma-net-update-regarding-Connec...
Best regards
Oskar Jansson
Copyright © 2022 Visma.com. All rights reserved.