Hi @adrianm, “What return code for timeout will be?”  504 Gateway Timeout. “If the timeout happens on PUT/POST, will the operation also be cancelled?” This depends on the business logic behind the endpoint. If there is no actual checking there - within the transaction or process - that the client still is connected, then the transaction should go through, even though the client got a timeout response. “OpenApi and versions” "v1" as version has been the same always and will probably still be for a while. It can be looked upon as the version of the ERP API, not to be confused with the v1 or v2 in the url, which points to a particular endpoint version, or the OpenAPI specification version which is the version of the (swagger) specification format.   Please let us know if you have any further questions.   Hi @thingsio ,  “I assume this will not change the token request URL too?” You are correct, the URL for the request token will stay the same.(https://connect.visma.com/connect/token)   Hi @jacob, “https://salesorder.visma.net/api/v3/ Wil this also move to https://finance.visma.net/ ?” The URL for Visma Net SalesOrder API will remain the same.(https://salesorder.visma.net/api/v3/) ... View more

We also have the same problem. We do not specify autoinvoice in the JOSN we send when we create customers, and we specify a CustomerClassId that does not say that autoinvoice should be true. Still it seems like that the customer gets the autoinvoice value based on if it is registered in ELMA. How can we in Visma .Net specify that it should be the CustomerClassId that should enforce autoinvoice settings for a customer? ... View more