Loading...
Area: Episerver Service API
Applies to versions: 4 and higher
Other versions:

Catalog nodes

Recommendations [hide]

This section describes how to work with catalog nodes in the Episerver service API, when defining catalog integration services for Episerver Commerce. See Catalog service for information about using the service integration for catalogs.

In this topic

Example models

Get All Nodes
/episerverapi/commerce/catalog/{catalogName}/nodes

By default this method gets all languages for the nodes and entries. If you want only one specific language, use the Accept-Language header.

Client Code Media Type Json

Response Json

Client Code Media Type XML

Response XML

Get Node
/episerverapi/commerce/nodes/{node code}

By default this method gets all languages for the nodes and entries. If you want only one specific language, use the Accept-Language header.

Client Code Media Type Json

Response Json

Client Code Media Type XML

Response XML

Post Node
/episerverapi/commerce/nodes

Client Code Media Type Json

Response Json

Client Code Media Type XML

Response XML

Put Node
/episerverapi/commerce/nodes/{node code}

Client Code Media Type Json

Response Json

Client Code Media Type XML

Response XML

Delete Node
/episerverapi/commerce/nodes/{node code}

Client Code Media Type Json

Response Json

Client Code Media Type XML

Response XML

Get common draft node [New in Service API 5.1.0]

Previously, the Service API supported published versions only. By adding new endpoints (listed below), you can get common draft versions, create new common drafts, and update or delete existing drafts.

Post common draft node [New in Service API 5.1.0]

Note: We do not support creating common drafts for non-existing content. You can create a first draft version by using an endpoint for published content (without “commondraft”) and setting IsActive to “false”.

Put common draft node [New in Service API 5.1.0]

Notes: If common draft content is in “Published” state, a new common draft version is created (same behavior as Post common draft). If common draft content is in DelayedPublish/AwaitingApproval/CheckedIn state, then it skips updating content and returns a Conflict status code (409).

Delete common draft node [New in Service API 5.1.0]

Do you find this information helpful? Please log in to provide feedback.

Last updated: Aug 14, 2017

Recommendations [hide]