New SOAP features, improving your performance and lots of other updates

January 21, 2016

Dear e-conomic API developer,

Welcome to the another edition of the e-conomic developer newsletter. We have a lot of new stuff in this issue - new SOAP features, new token naming, new App Identifier deadline, new Grant Access page and more.

App Identifier

New App Identifier deadline (Important!)

A lot of you have added the X-EconomicAppIdentifier HTTP header, as we have asked you to in previous newsletters. We really appreciate that. Unfortunately, we didn't see the level of compliance that we had hoped for, so we have decided to move the deadline for implementing the App Identifier header to:

March 15th 2016

By moving the deadline we give you additional time to implement the header, so you can prevent yourself and your users from being adversely affected when we start rejecting SOAP API requests that don't include this header.

Note that setting the App Identifier only applies if you are using a Connect method other than ConnectWithToken to connect to the SOAP API.

Learn more about App Identifiers and how to add them

Learn how optimized their performance with 20x

In our previous newsletter, we offered to assist you if you wanted to optimize the API usage of your integrations. Daniel Bahl from e-learning portal was one of the integration partners who contacted us and asked us to help him optimize his invoicing integration.

By using CreateFromDataArray methods to include multiples invoices and their properties in a single call, Daniel was able to reduce the amount of calls from his integration drastically.

In fact, looking at the entire invoicing flow from creating invoices and invoice lines, booking the invoices and retrieving PDFs, Daniel’s integration has gone from taking 50 minutes to process the invoices to just 2.5 minutes! And it has only taken him one day’s work to achieve this improvement.

Read more about optimizing your app to get better performance

New ways to fetch invoice lines and product prices

New ways to fetch invoice lines and product prices

To further help you improve your app performance, we have exposed a number of new methods in the SOAP API.

To fetch invoice, order and quotation lines in e-conomic, you previously had to get them one invoice/order/quotation at a time. We have made this easier and faster by exposing the following four methods in the SOAP API:

Each of these methods take an array of the appropriate sales document handles and returns all the lines that match these.

Learn more about the new methods for fetching invoice/order/quotation lines

Similarly, for product prices in different currencies, you have until now only been able to get a single price for a single currency at a time. To make it easier to fetch multiple product prices, we have exposed three new methods:

So if you wish to fetch all product prices for a specific currency, for example, you would first use ProductPrice_FindByCurrency to get all ProductPriceHandles and then ProductPrice_GetDataArray to fetch the actual prices.

Learn more about the new methods for fetching product prices

New naming for the API token model

We have offered token-based authentication for a long time now, and it has become apparent that the naming of these tokens causes some confusion. So we have tried to rename the tokens to something a little more intuitive.

Note that the old token names will continue to work despite the renaming.

These are the new names for the three types of tokens:

  • AppSecretToken: This is the token used by your integration when connecting to the API.
  • AppPublicToken: This is the token used by your integration when signing a grant token to grant an integration access to an agreement's data, and is included in the query string of the page you send to users.
  • AgreementGrantToken: This is the token resulting from a user granting your integration access to their data. It is either returned to the user after authenticating on the page you send them to, or included in the redirect URL you have specified.

Read more about the new token names and how to use them

Updated Grant Access page

New and improved Grant Access page

The Grant Access page allows your users to grant access to your app so it can access data in their agreement.

This page has long been in need of some attention, and we have now updated it in various ways:

  • Easier to understand for end-users, with info on the specific kinds of data the app will be able to access in the agreement, e.g. invoices, customers, products, etc - instead of just the names of the app roles
  • Updated and mobile-friendly layout with improved overview
  • Clearer and more specific error messages
  • Localization support so you can specify the language that the page should be displayed in by adding the locale query string parameter to the URL, e.g. /requestaccess.aspx?appid=[AppPublicToken]&locale=da-DK (supported languages are English, Danish, Swedish and Norwegian)

Learn more about the updates to the Grant Access page

Approve mileage entries through SOAP

If you have been using our SOAP API for integration with the Project module in e-conomic, you will know that it has been possible to approve time entries for a long time. But until now it hasn’t been possible to approve mileage entries through the API.

The new endpoint MileageEntry_ApproveEntries corrects this. The endpoint has the same signature as TimeEntry_ApproveEntries and takes an array of MileageEntryHandles as input.

See the documentation for the new endpoint

Split between e-conomic and Reviso completed

Last May, Visma acquired the Nordic business side of e-conomic, including the rights to the e-conomic brand. Following from this, e-conomic outside of the Nordic markets has now become a separate company called Reviso.

In the Nordic markets, e-conomic remains the same in terms of the code, URLs and the API. Outside the Nordics, however, we moved all code and data as well as created new URLs and endpoints for the API, with the changes taking effect on December 4.

What does this mean for my integration?

If you only have users from the Nordic countries, the split involves no changes for you, as these users remain as e-conomic customers. But if you should come across non-Nordic users, now Reviso users, trying to access your app, now you know why they won't be able to use your app.

If you do have users outside of the Nordics, we have already contacted you before the split and told you about your options for creating an app for your Reviso users.

Learn more about the split and how to create apps and get support for Reviso

Best regards,
Your e-conomic API team