Chapter endpoints
These endpoints allow you to track content consumption in context of chapters.
Usage of these endpoints require an active session. Make sure that you call the sessionStart
endpoint first to obtain a valid session ID.
chapterStart
The chapterStart
endpoint indicates the start of a chapter. See Media Edge API implementation examples for more examples calling this endpoint.
POST https://edge.adobedc.net/ee/va/v1/chapterStart?configId={datastreamID}
data-slots=heading, code
data-repeat=1
data-languages=CURL
Request
curl -X POST "https://edge.adobedc.net/ee/va/v1/chapterStart?configId={datastreamID}" \
--header 'Content-Type: application/json' \
--data '{
"events": [
{
"xdm": {
"eventType": "media.chapterStart",
"mediaCollection": {
"sessionID": "ffab5[...]45ec3",
"playhead": 0,
"chapterDetails": {
"index": 0,
"length": 0,
"offset": 0
}
},
"timestamp": "YYYY-08-20T22:41:40+00:00"
}
}
]
}'
If successfully processed, the API returns 204 No Content
.
This endpoint requires the following payload properties within the xdm
object:
eventType
media.chapterStart
for this endpoint.mediaCollection
timestamp
The mediaCollection
object requires several properties. See Media Collection Details data type in the Experience Data Model guide for more information.
sessionID
sessionStart
endpoint.playhead
chapterDetails
index
, length
, and offset
properties are required.chapterComplete
The chapterComplete
endpoint indicates the completion of a chapter. See Media Edge API implementation examples for more examples calling this endpoint.
POST https://edge.adobedc.net/ee/va/v1/chapterComplete?configId={datastreamID}
data-slots=heading, code
data-repeat=1
data-languages=CURL
Request
curl -X POST "https://edge.adobedc.net/ee/va/v1/chapterComplete?configId={datastreamID}" \
--header 'Content-Type: application/json' \
--data '{
"events": [
{
"xdm": {
"eventType": "media.chapterComplete",
"mediaCollection": {
"sessionID": "ffab5[...]45ec3",
"playhead": 0
},
"timestamp": "YYYY-08-20T22:41:40+00:00"
}
}
]
}'
If successfully processed, the API returns 204 No Content
.
This endpoint requires the following payload properties within the xdm
object:
eventType
media.chapterComplete
for this endpoint.mediaCollection
sessionID
and playhead
properties are required.timestamp
The chapterDetails
object is not allowed when using this endpoint.
chapterSkip
The chapterSkip
endpoint indicates that the user skipped a chapter.
POST https://edge.adobedc.net/ee/va/v1/chapterSkip?configId={datastreamID}
data-slots=heading, code
data-repeat=1
data-languages=CURL
Request
curl -X POST "https://edge.adobedc.net/ee/va/v1/chapterSkip?configId={datastreamID}" \
--header 'Content-Type: application/json' \
--data '{
"events": [
{
"xdm": {
"eventType": "media.chapterSkip",
"mediaCollection": {
"sessionID": "ffab5[...]45ec3",
"playhead": 0
},
"timestamp": "YYYY-08-20T22:41:40+00:00"
}
}
]
}'
If successfully processed, the API returns 204 No Content
.
This endpoint requires the following payload properties within the xdm
object:
eventType
media.chapterSkip
for this endpoint.mediaCollection
sessionID
and playhead
properties are required.timestamp
The chapterDetails
object is not allowed when using this endpoint.