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 makes 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.     Se this knowledgebase article for a complete guide on how to migrate your existing Visma.net ERP integrations:  Guide - Move from VNI to Visma Connect Authentication for Visma.net ERP API  ... Vis mer

If you are an organization working with developing integrations towards Visma APIs you might have the need to have multiple people in your organization accessing the Visma Developer Portal to perform different tasks. Visma Developer Portal accommodates this by allowing you to set up and organize teams that can access Visma Developer Portal for your company.   The My Team tab As a Team Manager for the team in Visma Developer Portal you can administer your team from the My Team-tab.    The tab includes three sections: My organization: Here you can see and edit the information that is registered for your organization. You can also upload an icon for the organization, this will be used on Visma App Store.  Certifications: In this section you will see the certification-status for your organization. Team members: Here you can administer the members and roles of your team.     Adding a new team member To add a new team member to your organization press the New member button. A new line will appear in the table and you can provide the first name, last name and email of the member. Save the new member by pressing the save button on the line.       Removing a team member To remove a team member press the garbage-can icon in the table. Confirm by pressing OK in the dialog. ... Vis mer

Introduction As a Visma ISV you have the opportunity to showcase your Visma-integrated applications on our Visma App Store (https://apps.visma.com). The Visma App Store is the end customers portal, where all customers of Visma products can find, activate and administer the applications and add-ons to their products.  For you as an ISV, we have a separate portal called the Visma Developer Portal (https://oauth.developers.visma.com/). This is your portal as developers and ISV where you can create and manage your applications, setup the API-connections required and manage the applications you want to have visible for the customers on the Visma App Store.  So think of the Visma App Store and Visma Developer Portal as two siblings aimed at different audiences, the App Store is for customers that want to find and use apps and integrations, the Developer Portal is for developers and ISV that wants to build and manage applications. In this guide we will give an introduction on how you can use the Visma Developer Portal to create new applications you want to display on the App Store or manage the existing applications you have. Step 1 - logging in to Visma Developer Portal To create or manage your applications as an ISV you must log in to the Visma Developer Portal. You can do this by either going directly to Developer Portal URL (https://oauth.developers.visma.com/) or via the Developer Portal icon on Visma Home.   Sign-in with your Visma Connect username and password or one of the other supported IDP-providers. If this is your first time logging in and you are not connected to an ISV Company you will have the opportunity to register your company as an ISV. Once inside the Developer Portal you will see the start page   Sections of the Developer Portal Inside the Developer Portal you will see the following sections in the top main menu. Start page This is the start-page where you will have an overview of your tasks and recent activity. APIs On this page the different Visma APIs that are available for you as an ISV to use for building your applications. For each API you will find detailed information. My Applications In this section you will have an overview of and the ability to create and manage all the applications you create. All applications you want to have available on the Visma App Store must be created and managed for here. My Team If you have more developers or other resources in your team that you want to have access to your applications in Developer Portal you can manage your team members here. Documentation Here you’ll find relevant documentation on how to use the Developer Portal and connecting to Visma APIs.   Step 2 - Create og manage your application from My Applications   In the My Applications section you will find a list of all the applications you have created and can manage, you can also create new applications from here.   To manage one of the applications press on the name of the application. Depending on the type of application, the details of the application will differ. For marketing type applications, meaning applications that are only available on the App Store and does not have any API configuration required the screen would look like this.   On the first tab you have some general information about the application, it will need to have an name, a unique client Id and a description. You can also change the logo of the application pressing the pencil-icon on the application icon. The next tab called Visma App Store is where you can create and edit the information available for the application on the Visma App Store.   As you can see this application is not yet available on the App Store, so let’s set this up by clicking on the Start setup for Visma App Store button.   The first thing we need to provide is an url to the developer website (your website) which can include more information about the application. We also need to provide one or more systems the application support and one more more categories for the application.   Once that has been completed, we can start configuring the markets (countries) where the application should be available in the App Store, by clicking New marketplace. Now you choose which country you want to make the application available to.   A new screen now appears that allows you to edit the information-page for the application.   Click on the description-section to edit this.   After you have edited the content of the description you get some more information you should append.   It is required that you add at least one pricing tier, you can also add a link to a page containing detailed pricing information. You can also add a list of benefits both for the application itself or each separate pricing tier. After you have added the information, you can save the information and request a review from Visma.   Once the review has been completed, the application will be available in the Visma App Store. ... Vis mer

Visma Software AS inviterer deg som ISV til å få en sentral posisjon under vår Tech Festival på Rebel i Oslo, torsdag 29. september.   For første gang arrangerer vi Visma Tech Festival, et partnerarrangement med 250 strategiske deltakere, hvor alle som er med på å redefinere fremtidens teknologi samles.   Detaljer rundt agenda og foredragsholdere kommer og vil fortløpende lanseres på en helt egen landingsside.   Vi har satt sammen to pakker. Ved påmelding følger mer detaljert informasjon etterkant.   Utstillerpakker:   Pakke 1: kr 49 000,- Inkluderer promofilm i vårt Visma Studio, visning av film under eventet, 5-10 minutter lightning talk i festivalområdet eller scene 2 og en stand til to personer (ordinær deltakerpris er 4300,-)   Pakke 2: kr 5 000,- Inkluderer logo i lokalene (deltakerpris kommer i tillegg) Vi gleder oss til nettverksbygging med deg på Tech festival!   Meld deg på her!    Har du spørsmål? Ta kontakt med en av oss: thomas.skjorten@visma.com tlf: 95795966 john.petter.kvanli@visma.com tlf: 97594252 torstein.stolan@visma.com tlf: 99591180 knut.gunnar.andersen@visma.com ... Vis mer

We are building a demo-application to help you get started with the Visma Business NXT GraphQL API. The application is a simple web-application built in Python using the Flask-framework.    Take a look!   https://github.com/Visma-Software-AS-Product/BusinessNXT_API_Examples ... Vis mer

Hei,    Vi inviterer til en ny HappyHour for ISV'er som er nysgjerrige på Visma Business Nxt APIet!   Meld deg på ISV Happy Hour her: Påmelding!    12.05.2022  kl. 1400 ISV Happy Hour VBC   ... Vis mer

Many of you have already seen, and some also started to use the new Visma.net Sales Order Service API to create and get information about salesorders in Visma.net Financials since we released the first version of the API in august of 2021.    The new API is the first part of our strategy to separate the existing Visma.net Financials API into smaller and more focused services for each part of the application.   The benefits of the new APIs are many. First of all the performance of the new APIs is on a whole different planet compared to the existing API, we see improvements of more than 20 times the performance when using the new API. The security of the new APIs are also significantly improved since we now use the Visma Connect authentication service for securing the access. The structure of the new APIs are also simpler to understand, and easier to program against.   Since the first release, we have been constantly improving and extending the functionality of the Sales Order Service API, and we will continue to do so at a rapid pace with multiple new releases every week. You can follow the release-notes here.   Today the functionality of  getting and creating salesorders are complete enough that every integration should be able to switch to the new API. This is why we now have started to plan the removal of the salesorder endpoints in the existing Visma.net Financials API. We know that changing all of your integrations, especially those using the important salesorder-endpoint are not a task that is done in a jiffy. So don’t worry, you still have time. In the current plan, we will start deprecating the old endpoints in 1st of June 2023.  Update: Move of breaking change Due date for Sales order v1 and v2   But please do not wait too long, the API is ready to use, and we would really want you to start moving over your integrations as soon as you can and start taking advantage of the benefits.   We’ve created a guide for you on how to get started with the new API, have a look and get started today.   You’ll also find the documentation here.   Happy coding!   Information about breaking changes: 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 DEC 31, 2024 ... Vis mer

Partner KickOff 2022 En sky for deg, en sky for våre kunder  I Vekst & Migrasjon   Placeholder til kickoff med Visma Software Hold av dagen 17. februar til kickoff. Vi skal feire det vi fikk til i et krevende og annerledes 2021, men først og fremst se på mulighetene som venter oss i tiden som kommer. 2022 kommer til bli migrasjonens år, der vi skal sammen migrere våre felles kunder til skyen.    Dato: Torsdag 17. februar 2022 Tid: Kl. 14:00–16:30 Kl 14 -16:30 (ink All Stars Awards) - Agenda for dagen kommer DIGITAL Event + Mulig social meetpoint Afterparty   Link til påmelding: https://app.myonvent.com/event/partner-kick-off-Lme0nFNIx  ... Vis mer

We are quickly moving towards the season which sets all retailers and e-commerce actors to the test of the year. The Friday after thanksgiving is the day when all retailers turn their accounts from red to black, hence the name Black Friday (according to the internet). So that means a lot of inventory have to move out of the shelves and a lot of money out of the customers pockets. Since the early Black Fridays, we have expanded the term to Black Weeks and added Cyber Mondays, which have become Cyber Weeks. You get the point, November and December are the months where the retail-systems are pushed to the limit, and your retail-integrations have to be in tip-top shape.   So what could be a better time to start using the new Visma.net ERP Sales Order API?   This brand new API is built specifically to improve the performance and usability of our APIs related to the process of creating salesorders. It is still a work-in-progress, meaning that new functionality will continue to be added to the API, but the functionality that is already there can make a huge difference for your applications.   Lets focus on a couple of endpoints that are vital to the e-commerce experience.   InventorySummary For a long time we've had the GET InventorySummary endpoint in the Visma.net API. The functionality of this endpoint is to get information about how the availability of a product is. How many are available for sale? How many are booked on salesorders? etc.  This endpoint is one of the absolute most used in the Visma.net API, and we traditionally see a peak during November and December.   But there are a few issues with the InventorySummary endpoint: It only allows for asking about one item per call (and also one warehouse, if you use multiple warehouses). This means that you have to make a lot of API-calls. It returns quite a bit of data, most often way more than you need. This means that the execution of the endpoint is quite slow, because a lot of data have to be collected from different corners of our database. We've seen the pains this results in for your integrations, and the buckets of sweat that our servers have produced trying to process all these requests. So please welcome the new endpoint in the Sales Order API... /Inventory.   The new /Inventory endpoint, have been developed to handle these needs with ease and brilliance.   Now you can: Get the Inventory-availability of as many items as you like per call. Get information about the availability across warehouses and location at once. Filter on warehouses and locations. Choose how much data is returned (include locations and/or attributes). Filter on availabilityModifiedSince. Filter on attributes. Get the results at blistering speeds. Blistering speeds you say, how fast is that exactly?   Well, we've done quite a bit of testing. In the old /InventorySummary endpoint we see that the average request takes around 1 second (1000ms). And then you get only 1 item from 1 warehouse.   On the new /Inventory endpoint we see the average time is 60 ms, and it doesn't care much if you ask for 1 or multiple items (60 ms is the average for getting 5 items). And then you get all the warehouses where the item is stored. You can expand the location-info and attributes as well, just a few more milliseconds of processingtime.   So in a real world example:   If you have a webshop and the customer have added five items to the shopping cart. Before checking out you would like to check the availability of the items. So with the old endpoint you would make 5 calls, each of around 1 second.  (If you have multiple warehouses, you can multiply this by the number of warehouses). In the new endpoint you make 1 call, for all five items, across all warehouses. That will take around 60 ms. That is 5000ms (5*1000) vs 60ms. I'd say that is blistering speed.    Salesorder But of course, checking the availability does not make the accounts go from red to black. Hopefully the customers will create a lot of salesorders as well.   In the new API we also have a POST /SalesOrder endpoint, that does exactly that. In the current version it supports all the functionality needed to create most salesorders (as long as it is of type SO). You can add discounts, currencies and notes along with the other information needed.   And as you would expect, this goes quite fast as well. We've found that creating an order is about 25 times faster with the new endpoint. And the more lines in the order, the more performancegain you will see.   And on a final note, since the new endpoints are so much more effective this doesn't stress our servers nearly as much. That means that we can handle tons of request without breaking a sweat. Good for us, good for you and good for the customer.     The new endpoints can be used side-by-side with the existing endpoints, so you don't have to rebuild everything. You can start by using only one of the new endpoints and then rebuilt your integration over time.   If you are not familiar with this new API, i suggest you start by reading this article Getting started with the first neXtGen service: Visma.net ERP Sales Order API .   You can also check out the documentation here: https://salesorder.visma.net/swagger/index.html.   Happy coding! Looking forward to setting new Black Friday sales records with you!           ... Vis mer

Hei,    Som mange av dere allerede vet har vi jobbet en stund med et produkt kalt Visma Business Cloud, selvfølgelig vil også dette produktet ha et svært godt API. Dette APIet er basert på GraphQL, dette gir nye muligheter for å bygge datadrevne integrasjoner.   Vil du lære mer?   Meld deg på ISV Happy Hour her: Påmelding!    18.11.2021 (november)  kl. 1230-1400 ISV Happy Hour VBC Introduksjon til Visma Business Cloud API'et, som er basert på GraphQL. Dette er spesielt for utviklere hos våre partnere (ISV/VAR/AO) ... Vis mer

Hei.    Det er en glede å ønske velkommen til årets Partner Cloud Camp for norske partnere! Invitasjonen og påmeldingen er nå åpen. Viktig at dere sprer denne informasjonen intern i deres organisasjon.    Meld deg på her!      Jeg håper vi ses digitalt den 16 september:-)   Med vennlig hilsen  Knut Gunnar Andersen ... Vis mer

When you have encountered an issue and it seems related to the Project Management UI Configurations or ISV needs to clarify financials company setup, license related matters before moving further with the API, the Project Management support / Partner Service should be contacted. In this case, please inform your Visma.net Project Management customer to contact Project Management Support or Partner Service from relevant market to get further information regarding the procedure that should be followed.   Partner service contact details for ISVs Country For ISVs (Partner Service) For Project Management users (Visma Partner) 🇳🇱Netherlands partnersnl@visma.com    Find your partner: https://nl.visma.com/erp/partners/ ERP Support: consultancynl@visma.com   🇳🇴 Norway kundesenteret@visma.no Find your partner: https://www.visma.no/erp/finn-din-partner/ ERP Support: Visma.net.support@visma.no 🇸🇪 Sweden vismanetisv@visma.com Find your partner: https://www.visma.se/affarssystem-i-molnet/hitta-partner-se/   🇫🇮 Finland sovellustuki@visma.com Find your partner: https://www.visma.fi/vismanet/jalleenmyyjapartnerit/ ... Vis mer

Visma.Net Project Management API Developer Support Community is a platform for integrators to raise questions, share ideas, experiences or provide feedback and hold discussions about Visma.Net Project Management API with other integrators and enthusiasts, provide tips for using API to the community and get help from other developers.   We encourage you to participate in ongoing discussions to help other users by sharing your knowledge or experience regarding the topics that you may have already faced and resolved. New user? If you are a new user, you can create an account by clicking the Sign In-button on the top of the page. Here you can choose to create account.   To get write-access to the community you have to contact your Partner Service from your related market. Provide your user-name for the community and you will be granted access to participate in the Forums and Ideas section. How to participate in the forum Create threads and posts related to the specific Visma.Net Project Management API topic that is the focus of that forum. To discuss another Visma product, you can visit that product’s forum. Post your Ideas, Feature Requests under the "Ideas" tab. Create posts that are related to the question or discussion to which you’re responding. Use "Search" to find questions or discussions that are related to your interests. If you are unable to find a related topic, start a new one by clicking New Topic. Create clear and concise topic subjects and posts. Subjects should not be in all capital letters. Include only important URLs. Posts with excessive/unrelated URLs will be removed. Do not include personal information. To ensure your safety, security, and privacy, never post your email address or any personal information you don’t want to share. Visma representatives won't ask for your password. Be cautious if you choose to contact others offline or ask others to contact you. Be respectful of others’ opinions. When disagreeing on an issue, stay polite and assume good intent. By using this community, according to GDPR, you confirm that your input will not contain sensitive or confidential information.   Please see Visma Community Terms & Conditions Visma Privacy statement Guidelines Visma.Net API Project Management Developer Forum participants are required to abide by the following guidelines. Breaking these guidelines might result in your post being removed. Severe abuses might lead to harsher penalties including warning or removal of access to the Visma.Net API Project Management Developer Support Community.   Do not send confidential customer data via threads, posts or chat. Do not send login/token information via threads, posts, chat or tickets Please keep your posts constructive and positive, as name-calling or personal attacks are not welcomed here Keep your messages concise and stay on the stated topic Respect copyright and do not post copyrighted information to the forums Search for posts on the same topic before posting a new question Post in the most relevant area for the relevant topic Members are asked only to post in English in our International Forums, as those belong to an English-speaking community The forums are actively moderated, but messages are not screened before they are posted Visma is not responsible for any errors or consequences caused by answers or information in this forum If you have an issue concerning our services, policies or staff, please use a personal contact method such as a private message or email to a staff member   Please also see, PM API documentation ... Vis mer