The RSP API
This document presents the interface used by Active Video Networks Cloud TV application developers to get access to the assets and their corresponding metadata.RSP exposes this interface through a web service with responses formatted as JSON objects. They follow the fundamental data structure of RSP (feed/post/asset and groups). This interface exposes only posts (and assets) with a “Ready” state, meaning that the media are available in all MSO’s edges.The access to the API is restricted to he perimeter of a content provider identified by an API key associated. Http call header must contain this key to be authorized.
Groups: Get All Groups
Returns a list of all groups uses by RSP authorized by the API key included in the header of the request (defines the content provider)
Syntax: http://<RSP server>/api/groups/list.json
Note: RSP does not currently manage a hierarchy of groups. Therefore, the parent/children are always empty.
Groups: Get Group By ID
Returns a list of feeds description that belong to the group.
Syntax: http://<RSP server>/api/groups/show/<Group ID>.json
Feeds: List all Categories In Feed
Syntax: http://<RSP server>/api/feeds/list_cat/<Feed Id>.json?<parameters>
Returns a list of all categories found in the ready posts of the feed. Within a specific post with multiple categories, those categories are separated by “||”. This call allows the developer to define which categories are available to search for assets (cf. previous call).
Posts: Get Post By "GUID"
Retrieves a ready post with the specified GUID. The GUID is preserved from the original source, so if cross referencing RSP ingested posts against another API, use the GUID to reference a post where you already have the GUID from the content provider.
Syntax://<RSP server>/api/posts/getByGUID /<GUID>.json