Filtering by Tag: api

Web API and file exports for Priceforge

Published on by Joannes Vermorel.

Priceforge, our dashboarding and pricing webapp, is under rapid evolution. In particular, two new features, related to process automation, have just been put in production. With those features, it is now possible to design a completely automated setup, where every day and without any manual intervention, dashboards get refreshed and where revised prices get imported back into the business systems.

Web API

Inspired from the design already in place for Salescast, Priceforge has now its own Web API (Application Programing Interface). The purpose of this API is to offer the possibility to programmatically control the execution of your Priceforge projects from a remote system.

For example, with this API, it becomes possible to write a script that runs outside Priceforge, which first uploads the latest data by FTP toward BigFiles - our file hosting service - and second, that triggers the execution of the relevant Priceforge projects.

This API follows usual REST patterns with JSON-formatted messages. For now, there are two methods:

  • /api/startrun which triggers a project execution.
  • /api/projectstatus which details the state of a project.

File export

Priceforge can perform advance calculations to compute revised prices or optimized item display ranks - our technology not limited to prices only. However, to make the most of Priceforge, those data need to be imported back into the relevant business systems, Magento or Prestashop for example.

Priceforge now supports a built-in mechanism to export data throught the file tile. A tile - in Priceforge - is one of the elementary blocks that compose a dashboard. For example, Priceforge supports very visual tiles such as barchart or linechart.

The tile of type file has two outputs. First, the tile gets displayed as a plain block within the dashboard. If this tile gets clicked, you download the file. Second, the file is pushed back to BigFiles at the specified location. For example:

show file "/foo/my-prices.tsv" with Id, Label, Price

This tiny Envision script defines a tile of type file which produces a file named my-prices.tsv that is pushed to the folder named /foo in BigFiles. This file then becomes available for download through FTP.

Categories: Tags: priceforge api bigfiles No Comments

Java Forecasting SDK released

Published on by Joannes Vermorel.

Our technology is designed for easy integration within any business app. In particular, our Forecasting API comes as REST, and it requires little coding to start toying with it.

In order to make the process even easier, we have just released our Forecasting SDK for Java. This SDK comes a tiny JAR - nearly stand-alone, just a single dependency toward XStream, a handy utility for XML serialization. The SDK is released as open source under the liberal BSD license.

Want to power-up your Java ERP / CRM / BI app?
Don't hesitate to let us know.

Categories: community, developers, open source, release, web services Tags: api forecasting java sdk technical No Comments

Forecasting API v3 is live (REST + SOAP)

Published on by Joannes Vermorel.

About 18 months ago, we were announcing the release of the API v2. Today, we are proud to announce that Forecasting API v3 is live.

Both Safety Stock Calculator and Call Center Calculator have been already upgraded toward API v3 starting from the versions 2.5 and above.

As a primary benefit the 1h wait delay between data upload and forecast download is no more. We recommend to upgrade toward the latest versions of those apps.

(note: our Excel add-in has not been upgraded yet)

The primary focus of this release is simplicity. Indeed, the API v2 had incrementally grown to +20 web methods with both a certain level of redundancy and a lack of separation of concern.

Then, over the last 18 months, thanks to our growing partner network, we discovered many minor yet annoying glitches in API v2 related to popular programming environments (Java, Python, C++, Apex, ...). Thus, we made sure API v3 would avoid designs that prove to be troublesome in some environments.

Also, API v3 comes with both REST and SOAP endpoints. Indeed, REST has emerged as THE approach to ensure maximal interoperability in modern web-oriented enterprise environments, and we are very committed in staying up to the industry standards.

Here are a few facts about API v3:

  • 8 web methods (and only 4 of them actually required to for production usage) while API v2 had +20 methods. Less methods mean less time to spend deciphering our API spec.
  • The .NET Forecasting Client for API v3 has been reduced about 1k lines of code against +10k lines of code for the previous API v2 version.

Since API v3 provides all the features of API v2 while being much simpler, we have already started to migrate all existing service in production toward API v3.

API v2 won't be available for new users any more, but we will make sure all customers in production are properly migrated before shutting down the service for API v2.

Don't hesitate to contact us if you need you need any assistance in this process.

Categories: service status, web services Tags: api rest soap No Comments