Hi, is it possible to send the "paymentMethodId" for a credit note Now, I use api/v2/customerinvoice to export invoices and api/v2/customerCreditNote to export credit notes (invoices with amount < 0)   api/v2/customerinvoice accepts the field "paymentMethodId" and our clients would like the same for credit notes but there is no such field there. So, it looks like a credit note inherits the "paymentMethodId" from the Debtor (Customer) but in reality, sometimes the client may have an incasso (automatic payment) but his particular credit not should be with another payment method. Can you please help me with this problem? Best regards, Iryna   ... View more

Hi, the question is about api export of Invoices and Credit notes: ScreenId=AR301000&DocType=INV  and ScreenId=AR301000&DocType=CRM&RefNbr=000029 I'm using this api points: api/v2/customerinvoice api/v2/customerCreditNote The customer is asking to export the field "Transito", its a Dutch translation Which field in the invoice/credit note data set can I use for it? ... View more

Is it possible to create an invoice "credit note" using https://integration.visma.net/API/controller/api/v2/customerinvoice ... View more

I have a question about POST request to https://integration.visma.net/API/controller/api/v1/customer After creating a new Customer (Debtor) you do not send the created record back, the response is just empty. In reality, it's very necessary to get the number of newly created Debtor back. e.g. for the next call (adding the invoice to the newly created debtor) I need to know the number of Debtor. Of course, I can suppose that the number of new Debtor is the one I sent in the field  "number": { "value": "220001"} BUT after a simple test in POSTMAN I see that the number can differ: the 'customer' record was created, I did not get any error back, but the Debtor got a different number then I sent, probably because of the number range problem. It may cause huge problems because during sending the invoices we will expect that Debtors were created with the number we sent. Can you recommend something for this case?   ... View more

Hi, I'm testing my api connection Client_id of my app is isv_7123 Test user irina@kovnet.nl This user successfully authorized via my app, and got a refresh and access tokens. But when I try to use this access token to get a list of all Customers https://integration.visma.net/API/controller/api/v1/customer curl -X GET \ https://integration.visma.net/API/controller/api/v2/customer \ -H 'authorization: Bearer eyJhbG*************zlg' \   then I get Error 401 { "ExceptionType": "IPPException", "ExceptionMessage": "Invalid audience", "ExceptionFaultCode": "12010", "ExceptionMessageID": "12010_7a8cc216-3b6c-442c-b2db-5ba636b9b88c", "ExceptionDetails": "" }     What is weird: the same user irina@kovnet.nl get the response from this api point on Swagger... What I'm missing? *** no, access token is not expired *** I saw that probably I have to send 'ipp-company-id' in the header but in Swagger example for https://integration.visma.net/API/controller/api/v1/customer I don't see this param and also have no idea where to find it. 'Context' endpoint that was mentioned for this purpose in video lessons seems to be obsolete. In another topic here someone from support also mentioned /connect/userinfo endpoint - but this one is also absent now. ... View more