/vismanetapi/setting-up-your-integration/end-of-life-notices section Deprecated features and notice about end of life 2025-11-28T09:42:38+01:00 # End of life notices Deprecated features and notice about end of life Welcome to our section dedicated to end-of-life and deprecation updates, a crucial hub designed to keep you informed about changes in our API´s, services, and features. ## Current notices | Description | Status | Timeline or date for discountinuation | Relevant details | |------------------------------------------------------|-----------------|--------------------------------------:|--------------------------------------------------------------------------------| | [Change base URL](Change-base-URL.en.md) | Approaching EOL | 31.12.2025 | Switch to new URL: [https://api.finance.visma.net](Change-base-URL.en.md) | | [SalesOrder V1/V2 endpoints](SalesOrder-V1-V2.en.md) | Approaching EOL | 31.03.2026 | Switch to [SalesOrder V3 API](https://salesorder.visma.net/swagger/index.html) | ## Archived notices | Description | Status | Timeline or date for discountinuation | Relevant details | |--------------------------------------------------------------------------------------|------------|--------------------------------------:|----------------------------------------------------------------------------------------------| | 4-min timeout restriction | Deprecated | 30.04.2025 | Use `background-api` for requests longer than 4 minutes | | Change webhook URL to https:// | Deprecated | 30.04.2025 | Change from Http:// to Https:// | | [Endpoint for webhook subscription removed](Endpoint-for-webhook-subscription.en.md) | Deprecated | 30.04.2025 | Maintenance of Webhook subscriptions from this time can only be done in Developer Portal UI. | | Background API | Deprecated | 30.04.2025 | Background API webhooks where erp-api-background header contains a URL | /vismanetapi/setting-up-your-integration/end-of-life-notices/salesorder-v1-v2 page 2025-11-28T09:42:38+01:00 # End of SalesOrder V1/V2 endpoints We **highly** recommend initiating the transition to the V3 API as soon as possible. By starting early, you'll not only be ahead of the curve but also gain the advantage of better time for testing and ensure a seamless integration before the deadline. This will give you flexibility and time to thoroughly test your integrations with the V3 API, helping to guarantee a smooth cutover when the time comes. > [!TIP] > Watch our [webinar](https://vimeo.com/1123203484/9ced1250e1?share=copy) regarding the change to SalesOrder V3 and our [documentation](../_index.en.md#documentationswagger) for the SalesOrder V3 API ## What are the changes? The following API endpoints are scheduled for removal: | Method | Endpoint | |--------|-----------------------------------------------------------| | GET | /v1/salesorder/{orderNbr} | | GET | /v1/salesorder/{orderType}/{orderNbr} | | GET | /v1/salesorder/{orderType}/{orderNbr}/rotrut | | GET | /v1/salesorder | | GET | /v1/salesorder/{orderType}/{orderNbr}/commissions | | POST | /v1/salesorder | | POST | /v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder | | POST | /v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder | | PUT | /v1/salesorder/{orderNbr} | | GET | /v1/salesorderbasic/{orderNbr} | | GET | /v1/salesorderbasic/{orderType}/{orderNbr} | | GET | /v1/salesorderbasic | | POST | /v1/salesorderbasic | | PUT | /salesorderbasic/{orderNbr} | | POST | /v2/salesorderbasic | | POST | /v2/salesorder | | POST | /v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder | | POST | /v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder | All necessary features has been integrated into the new Sales Order Service API. ## Why is this happening? To be able to meet the demand for more functionality as well as improved functionality in combination with the demand for higher throughput of transactions, we have to move from the Classic endpoints to NextGen endpoints. Our new SalesOrder V3 endpoint will offer **improved** functionality, increased security, and better **performance**. Put in other words, by retiring older endpoints, we can focus on delivering these enhancements without the constraints of maintaining outdated systems. In summary, this change ensures that you will benefit from the latest technology and innovations we offer. It’s part of our goal to provide you with a more robust, efficient, and future-proof service. ## How will this affect you? This change will require you to rewrite integrations that use the affected V1/V2 endpoints. For most instances, this change should be quite manageable. But for more complicated integration, this can be a time-consuming process with necessary testing to confirm that your integration is working as expected. ## What should you do next? **Identify:** Determine if your Visma Net Integrations utilize any of the V1/V2 endpoints listed below. **Plan:** If you are using the affected endpoints, start planning your project to migrate to the V3 endpoints. **Contact:** If you are a Visma Net customer, contact your partner or integration vendor to clarify the necessary steps for your specific instance. /vismanetapi/setting-up-your-integration/end-of-life-notices/change-base-url page 2025-11-28T09:42:38+01:00 # Change base URL ~~Old base URL: ~~ New base URL: Example: `GET https://api.finance.visma.net/v1/account` >[!Note] >The lack of “API/controller/api/” in the new URL. Make sure code is not denying [https://api.finance.visma.net](https://api.finance.visma.net) as a base URL, in case you have code that **follows** a location header on a response. When changing to API Management we will change the base URL. In the first period, we will have support for the current URL. We want all integrations to start using the new base URL. /vismanetapi/setting-up-your-integration/end-of-life-notices/endpoint-for-webhook-subscription page 2025-11-28T09:42:38+01:00 # # Endpoint for webhook subscription > [!IMPORTANT] >Maintenance of Webhook subscriptions can **only** be done in Developer Portal UI. The following endpoints will be deprecated | Method | Endpoint | |--------|------------------------------| | GET | /resources/v1/event | | GET | /resources/v1/subscription/* | | POST | /resources/v1/subscription/* | | PUT | /resources/v1/subscription/* | | DELETE | /resources/v1/subscription/* |