Understanding rail section type fields | NAGRAVISION Documentation Portal

Overview

Rail responses contain a number of different type fields. This page explains the differences between them.

The following image shows an example rail response payload. The numbered callouts denote the different *type fields.

The type field (#6 in the image above) denotes the rail section type. These are explained in Section types in Rail reponses.

In addition to the rail section type, there are several other type fields within the sections block. These are explained in the following table:

Item number (see diagram above)	Field	Description
1	`contentType`	The content type as defined in CPM. Examples of content types include: `"movie"`, `"series"`, `"event"`, `"unknown"`, `"episode"`, `"tvshow"`, `"sports"`, `"highlight"`, and `"match"`.
2	`playbackType`	The playback type for the content item. Possible values: `live-event` `live-stcu-event` `vod-ed` `vod-ltcu` `npvr-event` `channel` This is set in the payload that the client sends to UAV when creating bookmarks. Rails Builder then uses this type when retrieving content from MDS to support use cases like continue watching. Also used by ION to drive behaviour in the user interface.
3	`modelType`	Deprecated: indicates CPM editorial or technical model. To be removed.
4	`type`	Deprecated: this is an internal type used within Rails Builder.
5	`entityType`	Deprecated: customer-specific value. This has a default that is set in Content Builder itself. To be removed.
6	`type`	Describes the type of the rail section. See Section types in Rail reponses.