Quan Mai
Optimizely
Oct 5, 2017
visibility 5669
star star star star star
(7 votes)

Announcing Order extension for ServiceAPI

ServiceAPI has been a popular RESTful APIs for Episerver Commerce, and it has been used by many websites, allowing easy and reliable integration with external systems. However up until now, only Catalog-related APIs (and a small set of CMS asset and content APIs) were supported. We have been asked about adding the support for order-related APIs to ServiceAPI.

And with ServiceAPI 4.1.0, that actually happens. We are happy to annouce that the order-related APIs are now available in ServiceAPI. You can install ServiceAPI 4.1.0 for Commerce today: http://nuget.episerver.com/en/OtherPages/Package/?packageId=EPiServer.ServiceApi.Commerce 

The new APIs included in this release are:

  • Cart: CRUD and search APIs
  • Purchase Order: CRUD and search APIs
  • Payment Plan: CRUD and search APIs
  • Contact and organization: CRUD APIs

More information regarding these new APIs can be found here: http://world.episerver.com/documentation/developer-guides/Episerver-Service-API/order-restful-operations/ 

We would like to express our thanks to Geta for their contribution to the extension.

Note that those APIs, while they can help you do many things with order system, are not "complete" or without limitation. We will continue adding more features, improvements, and bug fixes to upcoming releases. If you have suggestions or feedback, you are welcome to share them with us.

Oct 05, 2017

Comments

K Khan
K Khan Oct 5, 2017 12:38 PM

Future is in clouds :) For me, this is another step to reach the height of clouds, is there any stories around Campaigns/Promotions in backlog?

Quan Mai
Quan Mai Oct 5, 2017 02:01 PM

Campagins/Promotions are basically CMS content, which is something we wanted to support, but not in the near future ... 

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026

Opal Workflow Agents And The Graph Webhook Trap

What we did? We built a compliance review workflow agent in Opal. The job was simple: when an editor submits a page for review in Optimizely CMS 13...

Ritu Madan | Oct 14, 2026

cms13-scan: A Deterministic CMS 13 Readiness Scanner

Every CMS 12 to CMS 13 upgrade I have looked at starts the same way. Someone opens the solution and starts hunting. A text search for the APIs

Adnan Zameer | Oct 12, 2026 |