About Yıldırım

Yıldırım · ‎05-01-2023

Hello Dante, to correct the information I've shared, the base URL will still be the same, but the request headers should be set as shown below. (Visma Connect Token stores the Company details) curl -X 'GET' \ 'https://integration.visma.net/API/controller/api/v1/account' \ -H 'accept: application/json' \ -H 'authorization: Bearer xxxxxxxxxxxxxxxxx'

Yıldırım · ‎05-01-2023

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.

Yıldırım · ‎04-01-2023

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)

Yıldırım · ‎04-01-2023

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 · ‎04-01-2023

Hello, please share information on the following points. Used API Endpoint URL / Method Returned Http Status Code Returned Response Body (Error Message) If this is a POST/PUT request, then Used RAW JSON script has to be attached Thanks.

Yıldırım · ‎03-01-2023

Hi Stian, I see. Have you tried sending a PUT request ? "vatId": { "value": null },

Yıldırım · ‎03-01-2023

Hello, we confirm the issue. This has been reported to the development team. We will provide further updates as more information is available.

Yıldırım · ‎03-01-2023

because API is using the Customer Balance Report to retrieve the data based on the current fiscal year/period so that company you're sending the API request should have them defined.

Yıldırım · ‎03-01-2023

Release Notes Documentation Payment Amount in currency and Balance in currency added to the GET CustomerPayment endpoint The paymentAmountInCurrency and availableBalanceInCurrency have been added to the GET CustomerPayment endpoint. If you are using OneStopReporting, this now allows you to create reports like Aged past due (AR63100). Delete operation implemented for supplier details in PUT Inventory endpoint The Delete operation has been implemented for the supplier details in the PUT Inventory endpoint, which can be used to delete supplier information on a specific inventory item. Due dates for breaking changes Release Notes Documentation Due Remove deprecated parameters in Financial Period endpoint The numberToRead and skipRecords parameters for the financial period endpoint are deprecated and will be removed. Feb 28, 2023 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023

Yıldırım · ‎03-01-2023

Hi, Payloads may vary depending on your Financials ERP Company that you send the request. For instance, if the company is using autoNumbering for the customer, then the number field is not necessary to be used in the payload. However, here you can see a generic POST Customer JSON. Make sure to adjust the fields based on your company data. { "number": { "value": "106221" }, "name": { "value": "CustomerNameTest" }, "status": { "value": "Active" }, "vatRegistrationId": { "value": "999999999" }, "corporateId": { "value": "999999999" }, "overrideWithClassValues": true, "customerClassId": { "value": "1" }, "mainAddress": { "value": { "addressLine1": { "value": "Test" }, "postalCode": { "value": "6270" }, "city": { "value": "BRATTVÅG" } } }, "mainContact": { "value": { "name": { "value": "TestName" }, "attention": { "value": "TEST" }, "email": { "value": "test@visma.com" }, "phone1": { "value": "11111111" }, "phone2": { "value": "22222222" } } }, "deliveryAddress": { "value": { "addressLine1": { "value": "Ulla" }, "addressLine2": { "value": "222" }, "addressLine3": { "value": "333" }, "postalCode": { "value": "6290" }, "city": { "value": "HARAMSØY" } } } }

Yıldırım · ‎03-01-2023

Hi, have they generated financials periods for 2023 in their company ?

Yıldırım · ‎03-01-2023

Hello, As it can be seen in the Financials UI, if createVatTransactions is being checked then VatID, VatCategory etc. are populated in the line. So if you don't want to create that, then please use the following field in the payload and do not include VAT fields in the JSON. "createVatTransaction": { "value": false }, "skipVatAmountValidation": { "value": true },

Yıldırım · ‎02-01-2023

Hi, we've tested in swagger, the "Location" header is available in the Response Headers upon a successful POST request. POST SalesOrder V1 POST SalesOrder V2

Yıldırım · ‎02-01-2023

Hi, after following the steps explained in the documentation, token can be generated with the specified schema. Getting started with Visma Developer Portal see: 4.3 Generating a new API Token ----------------------------------------------------------------------------------------------------- URL: POST > https://connect.visma.com/connect/token 1) Request Headers Content-Type : application/x-www-form-urlencoded 2) Request Body a) client_id : ClientID (Generated in Developer Portal) b) client_secret : ClientSecret (Generated in Developer Portal) c) grant_type : client_credentials d) scope : application scope (can be seen in the developer portal) (Depending on what scopes have been allowed by the tenant administrator in the Visma App Store for your application.) -----------------------------------------------------------------------------------------------------

Yıldırım · ‎02-01-2023

Tenant ID can be seen by the Financials ERP Company user (customer) in the App Store, after its role has been assigned. Please see the following sections in the Getting started with Visma Developer Portal 3.4 How to assign “App Store: Integration Administrator Role" 3.6 Get the Company / Organizationʼs “Tenant ID”

Yıldırım · ‎28-12-2022

Hi, this is due to your application hasn't been approved in the portal yet. The integration request should be approved soon, then you can retry the token request. For more information, please review the Developer Portal documentation & Visma.net ERP API Developer Portal Startup Guide

Yıldırım · ‎21-12-2022

I see, could you send your API Client ID & Company ID to developersupport@visma.com, so we'll check the logs in detail Thanks.

Yıldırım · ‎21-12-2022

Hi, that's true, as long as company setup allows such as oriented with the Segment (Subaccount) validation & default values.

Yıldırım · ‎16-12-2022

Release Notes Documentation Branches added to SupplierPayment endpoint You are now able to GET/POST/PUT the Branch field via the SupplierPayment endpoint. GET SupplierInvoice: New fields added related to deferralSchedule The fields deferralSchedule and deferralScheduleNbr have been included in the GET SupplierInvoice endpoint. Earlier, only the deferralCode was retrieved. The "ScheduleID" from database displayed in deferralSchedule The "Schedule Number" from UI displayed in deferralScheduleNbr Purchase orders with the status Cancelled can no longer be added to purchase receipts Purchase orders with the status Cancelled can no longer be added to purchase receipts. Due dates for breaking changes Release Notes Documentation Due Remove deprecated parameters in Financial Period endpoint The numberToRead and skipRecords parameters for the financial period endpoint are deprecated and will be removed. Feb 28, 2023 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023

Yıldırım · ‎16-12-2022

Visma.net ERP APIs are now available for Visma Connect authentication in Developer Portal Since the Visma.net ERP API was released, authentication has been handled by an implementation of the OAuth 2.0 protocol called VNI. This has served us well, but it has some limitations that make it somewhat cumbersome to work with, both for you as developers and internally in Visma. Since the release of the Visma.net ERP API, the importance of APIs and number of integrations has grown rapidly and the amount of traffic we have received on the API has doubled year over year. More importantly, the requirements to securing the APIs are constantly increasing, and protecting our customers' data is always a top priority for us. In the last few years, we have developed our Visma Connect product into a state-of-the-art implementation of the OAuth 2.0 protocol, including surrounding tools like the Visma Developer Portal and Visma App Store. Using Visma Connect as the authentication provider for the Visma.net ERP API is therefore an important step to keep your integrations and our customers' data secure. Please see the following guides on how to Start & Migrate your Visma.net ERP API integrations: Guide - Moving from VNI to Visma Connect Authentication for Visma.net ERP API Getting started with Visma Developer Portal Following documents & Information will be useful when starting & migrating integrations. Present your application on Visma Home Managing your team in Visma Developer Portal Creating and managing apps on Visma App Store

Yıldırım · ‎16-12-2022

Hello Rene, could you retry your transaction and inform us accordingly ?

Yıldırım · ‎15-12-2022

Hi, we'll check it out.

Yıldırım · ‎14-12-2022

Hello Rene, we confirm your report that SalesOrder Service API doesn't seem fetching the default subaccount values when those are not provided in the POST Json, even though the Subaccount is set as "nullable" in the model (NewSalesOrderCommand). This has been reported to the Sales Order Service API team, we'll keep you informed.

Yıldırım · ‎14-12-2022

Thanks Magnus, this will be reviewed.

Yıldırım · ‎14-12-2022

Hello, have you tried updating/creating with the salesPerson first then sending PUT request for the subaccount ?

Yıldırım · ‎13-12-2022

Release Notes Documentation Notes field available to edit for ISVs in Stock items window In the Stock items (IN202500) window, the Notes field on the blue ribbon in the upper right corner is now available to edit for ISVs. Purchase orders with the status Closed can no longer be added to purchase receipts For endpoint POST /api/v1/PurchaseReceipt/[PurchaseReceiptNbr]/action/addpurchaseorder, you can no longer add purchase orders with the status Closed to purchase receipts. Due dates for breaking changes Release Notes Documentation Due Remove deprecated parameters in Financial Period endpoint The numberToRead and skipRecords parameters for the financial period endpoint are deprecated and will be removed. Feb 28, 2023 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023

Yıldırım · ‎13-12-2022

Hello Magnus, how long after are you making printShipmentConfirmation request, after dropshipment receipts created ?

Yıldırım · ‎12-12-2022

Thanks for the confirmation!

Yıldırım · ‎08-12-2022

Hello, could you please send us your API Client ID that you've generated a token with ? <developersupport@visma.com> Visma.net ERP API Throttling Policy can be seen here: Why am I receiving "HTTP 429 - Too many request / throttling" response from API ?

Yıldırım · ‎05-12-2022

Hello Magnus, thank you for mentioning this, could you also please share your JSON ?

Svar: https://integration.visma.net/API/service/ s...

Vastaus: Getting 5520 for sending timeCard

Re: Getting 5520 for sending timeCard

Vastaus: Getting 5520 for sending timeCard

Re: Getting 5520 for sending timeCard

Re: JournalTransactionLine without VatCode

Re: Error in PUT Shipment endpoint

Re: customer/balance error

[Release Notes] - Visma.Net API 9.28.0 - 01.03.202...

Re: Example data for POST customer?

Re: customer/balance error

Re: JournalTransactionLine without VatCode

Re: Creating SalesOrder - Response with newly crea...

Re: https://integration.visma.net/API/service/ see...

Vastaus: Authentication

Re: Authentication

Re: Print shipment confirmation sometimes returns ...

Svar: SalesOrder api subaccount issue mandatory

[Release Notes] - Visma.Net API 9.27.0 - 20.12.202...

Visma.net ERP API Developer Portal Startup Guide

Re: SalesOrder api subaccount issue mandatory

Re: Response compression does not work with batch

Re: SalesOrder api subaccount issue mandatory

Re: Bug: API allows for duplicate serial numbers i...

Re: subaccounts salesorder lines

[Release Notes] - Visma.Net API 9.26.0 - 13.12.202...

Re: Print shipment confirmation sometimes returns ...

Re: Same request made too many times

Re: Same request made too many times

Re: Bug: API allows for duplicate serial numbers i...

Useful pages

About Visma

Contact us

Follow us