Mari Jørgensen
Oct 7, 2014
visibility 4423
star star star star star star
(2 votes)

Working with the EPiServer 7.5 Commerce API

With the introduction of EPiServer 7.5, EPiServer Commerce provides a content provider that can serve any catalog content as IContent. This means that it is possible to work with catalog content using the same techniques as working with CMS content.

Read moreand view code samples by visiting the blog post on our company blog:
http://geta.no/blogg/working-with-the-episerver-7.5-commerce-api/

Oct 07, 2014

Comments

Eric
Eric Oct 7, 2014 04:32 PM

Nice, but could you please turn of the popup when refering from World ;)

Mari Jørgensen
Mari Jørgensen Oct 7, 2014 05:33 PM

Good point, Eric. I will see if it´s an easy fix for that.

Petter Klang
Petter Klang Oct 8, 2014 10:49 AM

Visitor groups perhaps? ;)

error Please login to comment.
Latest blogs
Optimizely Content JS SDK v2.1.0 — What's New and Why It Matters

  v2.1.0 of the Optimizely Content JS SDK and CLI landed on July 7, 2026. This is a substantial release bringing a wave of capabilities for...

Vipin Banka | Jul 8, 2026

Integrating a Third-Party DAM into Optimizely CMS 12: A Case Study

There is no handbook for wiring an external DAM into Optimizely CMS 12. This case study walks through the research, dead ends, and breakthroughs —...

WilliamP | Jul 7, 2026 |

Ringing a Physical Sales Bell from Optimizely Commerce

This one started as a weekend project that got a little out of hand. I built an “On Air” sign for my office — one of those LED signs streamers use ...

KennyG | Jul 6, 2026

Exploring Asset Lifecycle Management Approaches for Bynder and Optimizely SaaS CMS

Note: This is Part 3 of our Bynder integration series. For setup and filtering prerequisites, see Part 1  and  Part 2 . Introduction In my previous...

Vipin Banka | Jul 5, 2026