My Products
Help
veikkosa
VISMA

Getting 5520 for sending timeCard

by veikkosa

At least one of our customer gets error 5520 when integration is trying to send timeCard to visma.net

 

Response for request 'https://integration.visma.net/API/controller/api/v1/timeCard?week=202248' {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_c8d18cfa-ec5f-4cc6-a23f-cf2f77e8cc42","ExceptionDetails":""}

 

any ideas? Company ID is 2873461

12 REPLIES 12
veikkosa
VISMA

by veikkosa

well.. I discarded the token and our client created a new one and now integration is working ... So it will remain a mystery why the old token did not work and why the error message was so uninformative .. but thanks anyway 👌

Yıldırım
VISMA

by Yıldırım

Good to hear, please send your API Client ID & Financials ERP Company ID to developersupport@visma.com so that we can investigate in detail.

veikkosa
VISMA

by veikkosa

I tested randomly other endpoints with the token and all routes respond the same 5520

veikkosa
VISMA

by veikkosa

1) same error for GET https://integration.visma.net/API/controller/api/v1/timeCard/0000009

2) dunno .. I don't know any other endpoints 😁

3) don't know anything about that .. I do not have access to visma.net ..

Yıldırım
VISMA

by Yıldırım

Please authenticate at swagger and try the above-mentioned points. You can also use the same credentials to log in Financials ERP UI to check module access. 

veikkosa
VISMA

by veikkosa

but I cannot authenticate as our customer ... 

 

Don't you have any logs about error 500? This issue blocks our customer totally using our service and the error integration is responding does not give any clues about what is wrong .. only generic 

5520 😣

... I would say that if api returns error 500 it always means that there is something wrong with the api itself ..

 

Same integration is working ok for other clients...

Yıldırım
VISMA

by Yıldırım

You should be able to test the other endpoints with the current token that you're using.

When it comes to the logs, we're unable to see further details of what might cause this. Since this is only happening on the specific client, this is most likely related to that user & the company. 

 

Please send your API Client ID & Financials ERP Company ID to developersupport@visma.com

 

Regarding the troubleshooting, please review the article API incidents - Troubleshooting and reporting

We need information on these details to be able to help you. 

Every integration should have their own specific user to generate token with, so that please contact your client to login them via Swagger & Financials ERP UI to check access related parts. 

 

Thanks. 

Yıldırım
VISMA

by Yıldırım

1) Do you receive the same error when you try e.g. GET Specific Timecard ?

https://integration.visma.net/API/controller/api/v1/timeCard/0000009

2) Are the other endpoints working fine ? 

 

3)Does the Financials ERP User have access to the module, that has been used for generating the token ? 

So that, please try reaching out to the "Employee time card" Module in the UI after logging with the same user.
(ScreenId=EP305000)

veikkosa
VISMA

by veikkosa

veikkosa_0-1672829782874.png

very easy to reproduce with postman ... 

veikkosa
VISMA

by veikkosa

1. GET https://integration.visma.net/API/controller/api/v1/timeCard?week=202248

2. 500

3. {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_ec042a54-92bc-4f25-afcc-4ddc8fb63d4c","ExceptionDetails":""}

4. curl 'https://integration.visma.net/API/controller/api/v1/timeCard?week=202248' -X GET -H 'Authorization: Bearer xxxxx' -H 'Accept: application/json' -H 'content-type: application/json' -H 'ipp-application-type: Visma.net Financials' -H 'ipp-company-id: 2873461' --compressed

Yıldırım
VISMA

by Yıldırım

Hi, endpoint is responding well in our tests, have you retried the request ? Can you also try it out of your integration, such as in swagger or postman ?   

Yıldırım
VISMA

by Yıldırım

Hello,
please share information on the following points.

  1. Used API Endpoint URL / Method
  2. Returned Http Status Code
  3. Returned Response Body (Error Message)
  4. If this is a POST/PUT request, then Used RAW JSON script has to be attached
Thanks.