API Programmer Guide for Cisco Digital Signs

Transcription

1 Cisco Digital Media Suite API Programmer Guide for Cisco Digital Signs Version Revised: September 13, 2010 Contents About This Guide... 2 Who Should Use This Guide... 2 Introduction to Cisco DMS APIs... 2 Getting Started... 2 Installation Notes... 3 Before You Begin... 3 Checking API Status... 4 Workflow... 4 Making a Web Service Call... 4 Digital Signs APIs... 5 DMP Groups... 6 DMPs Content Asset Provisioning Application provisioning Playlist Provisioning Insertions and Requestors Proof of Play Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 28

2 Schedule Provisioning Emergency About This Guide Cisco Digital Signs is one component of Cisco Digital Media Suite (Cisco DMS). This guide describes Cisco APIs for third-party application developers whose products should extend or interoperate with Cisco Digital Signs. These APIs are a mechanism to insert, retrieve, update, and remove data. Similar guides on Cisco.com describe the APIs for other components of Cisco Digital Media Suite, such as Cisco Show and Share. Who Should Use This Guide This guide is a technical resource for application developers who build custom user interfaces, workflows, and vertical-specific applications that extend Cisco Digital Signs. You should have an advanced level of understanding of web technology, operation, and terminology and be familiar with Cisco Digital Signs. Application developers who use this application programming interface (API) should also have an understanding of a high-level programming language, such as Java or an equivalent language. Additionally, we recommend that you have knowledge of the following: XML and XML Schema Representational State Transfer (REST) and RESTful Services You should be familiar with using Cisco Digital Signs to manage your digital signage network. In most cases, API operations correlate to GUI operations. Introduction to Cisco DMS APIs This API uses the REST architecture, which leverages XML, HTTP, and HTTPS. This API executes requests by sending XML data to the API server. The server returns an XML response that combines an encoded REST message with an HTTP status code that states whether your request succeeded or failed. You can use this API to perform some of the same operations that are available in the web-based user interface for Cisco Digital Signs. NOTE Our implementations of Cisco DMS APIs might change over time in response to the changing needs of our partner community. We will maintain backward compatibility whenever possible but we encourage you to expect differences in future releases. Getting Started Topics in this section describe how to begin provisioning services with this API, verify the status of the API, and learn the steps in a typical workflow Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 28

3 Installation Notes Cisco Digital Signs includes all components for its own API. Aside from the requirement for a Cisco Digital Media Manager (DMM) appliance that is configured and operating correctly, this API imposes no additional startup or shutdown requirements. The only user interfaces for this API are XML-encoded messages. Before You Begin ATTENTION All applications that use API calls for Cisco Digital Signs must pass their XML data with the content type set to application/xml Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 28

4 Checking API Status NOTE Cisco Systems neither supports nor offers any warranties for DMS API Tester. Our partner community built and maintains this software utility. To test the APIs: 1. Download the Adobe AIR runtime from and install it on your computer. 2. Download DMS_API_Tester.air from 3. Install DMS_API_Tester.air., and then open it. 4. Complete these steps in DMS API Tester: a. Enter the fully qualified domain name (FQDN) of your DMM appliance in the Hostname field. For example: digitalsigns.cisco.com b. Enter the administrator s username. For example: superuser c. Enter the administrator s password. d. Choose xtas-core/services/ From the Service list. e. Choose dmpgroup_getall from the Template list. f. Click Submit. g. Accept the security alert. h. Verify that you receive a response like this one: <?xml version="1.0" encoding="utf-8"?> <DmpGroup> <id>4</id> <name>all DMPs</name> <uri> </DmpGroup> Workflow Each Digital Signs API call requires user authentication through the HTTP Basic Authentication method. Your application should pass in the username and password on each API call to guarantee a valid logged in user. All Digital Signs APIs (except multipart file uploads) support and should use HTTPS over port Making a Web Service Call The simplest way to make a web service call is to install the DMS API Tester AIR application. See Checking API Status above. This application helps you to test your API calls. ATTENTION Digital Signs uses a self-signed SSL certificate in Cisco DMS 5.2. This triggers a security alert when the first request is made using the DMS API Tester. You must accept this warning manually every time you launch the DMS API Tester and you must also ensure programmatically that your API calls accept this self-signed certificate Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 4 of 28

5 Digital Signs APIs Topics in this section describe APIs for operations that are specific to Cisco Digital Signs. These APIs are RESTful. This means that: You must set the content type for each request to application/xml. Each request leverages some combination of POSTs, s, PUTs, and DELETEs. Additionally, there are four main base entry points for Digital Signs servicers. /xtas-core/services/ /xtas-core/api/rest/ /proofofplay_core/services/ /proofofplay_campaign/services/ 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 5 of 28

6 DMP Group Provisioning DMPs are organized in logical groups. This approach favors simultaneous deployments to all members of a DMP group. A less efficient and scalable approach is to schedule sequential deployments that target individual DMPs one-by-one. Get All DMP Groups This API returns the hierarchy of your DMP groups. The ALL DMPs group at the root of this hierarchy contains all DMPs that are known to your DMM appliance. /xtas-core/services/dmpgroup/hierarchy/all/ The intended audience for this programmer guide can anticipate and understand the result that this API call returns. Nonetheless, we might document this result in a future revision to this guide. Add DMP Group This API allows for the creation of a new DMP group. POST /xtas-core/services/dmpgroup/dmpgroups/ parentid: the ID of the parent group name: the name of the dmp group description: the description of the group <n1:dmpgroup xmlns:n1=" <name> DMP_GROUP_NAME </name> <parentid> DMP_GROUP_PARENT_ID </parentid> <description> DMP_GROUP_DESCRIPTION </description> </n1:dmpgroup> The intended audience for this programmer guide can anticipate and understand the result that this API call returns. Nonetheless, we might document this result in a future revision to this guide. NOTE We do not perform any validation for the parent ID value. Please ensure that you pass only valid parent IDs Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 6 of 28

7 Update a DMP Group This API allows one to update a DMP group. PUT /xtas-core/services/dmpgroup/dmpgroups/{id} id: the ID of the dmp group parentid: the id of the parent group name: the name of the dmp group description: the description of the group <n1:dmpgroup xmlns:n1=" <id> DMP_GROUP_ID </id> <name> DMP_GROUP_NAME </name> <parentid> DMP_GROUP_PARENT_ID </parentid> <description> DMP_GROUP_DESCRIPTION </description> </n1:dmpgroup> The intended audience for this programmer guide can anticipate and understand the result that this API call returns. Nonetheless, we might document this result in a future revision to this guide. NOTE Update DMP Group only updates: name, description, and title. It does not update parent Id. Delete a DMP Group This API allows for the deletion of a new DMP group. DELETE /xtas-core/services/dmpgroup/dmpgroups/{id} Get DMPs that belong to a group This API allows for fetching all the DMPs that belong to a particular DMP Group. /xtas-core/services/dmpgroup/dmps/dmpgroup/{id} id: the ID of the group Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 7 of 28

8 Assign DMPs to a DMP groups This API allows for assigning existing DMP(s) to existing DMP Group(s). PUT /xtas-core/services/dmpgroup/dmpdmpgroup associationaction: make sure this set to set dmpidlist id: the ids of the dmps you want to add to the dmp groups dmpgroupidlist id: the ids of the dmp groups you want the dmps added to. <n1:dmpgrouptodmpassociation xmlns:n1=" <associationaction>set</associationaction> <dmpidlist> <id> DMP_ID_1 </id> <id> DMP_ID_2 </id> </dmpidlist> <dmpgroupidlist> <id> DMP_GROUP_ID_1 </id> <id> DMP_GROUP_ID_2 </id> </dmpgroupidlist> </n1:dmpgrouptodmpassociation> Unassign DMP from DMP Group This API allows for removing existing DMP(s) from existing DMP Group(s). PUT /xtas-core/services/dmpgroup/dmpdmpgroup associationaction: make sure this set to unset dmpidlist id: the ids of the dmps you want to remove from the dmp groups dmpgroupidlist id: the ids of the dmp groups you want the dmps removed from. <n1:dmpgrouptodmpassociation xmlns:n1=" <associationaction>unset</associationaction> <dmpidlist> <id> DMP_ID_1 </id> <id> DMP_ID_2 </id> </dmpidlist> <dmpgroupidlist> <id> DMP_GROUP_ID_1 </id> <id> DMP_GROUP_ID_2 </id> </dmpgroupidlist> </n1:dmpgrouptodmpassociation> 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 8 of 28

9 Assigning DMP configuration parameters to DMP Groups This API sets configuration parameter(s) to all the DMPs in a DMP group. PUT /xtas-core/services/dmpgroup/dmpgroupsconfig/ dmpgroupidlist id: the ids of the dmp groups you want the dmps removed from. Valid parameter(s) and value(s) to set and in the correct order <n1:dmpconfigure xmlns:n1=" <dmpgroupidlist> <id> DMP_GROUP_ID_1 </id> <id> DMP_GROUP_ID_2 </id> </dmpgroupidlist> <parameters> <nvp> <name> MIB_1 </name> <value> MIB_VALUE_1 </value> </nvp> <nvp> <name> MIB_2 </name> <value> MIB_VALUE_2 </value> </nvp> </parameters> </n1:dmpconfigure> NOTE The values and parameters are defined in the Digital Media Player API documentation Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 9 of 28

10 DMP Provisioning DMPs are the most granular target that can be used to deploy an application to a screen. Get DMP Details This API gives details about the DMP configuration: Name, IP address, MAC address, description and status (up or down). /xtas-core/services/dmp/dmps/{id} id: the ID of the dmp Add a DMP This API allows you to add a DMP to Digital Signs POST /xtas-core/services/dmp/dmps name: the name of the dmp you are adding ipaddress: the ip address of the dmp you are adding macaddress: the mac address of the dmp you are adding description: the description of the dmp you are adding <n1:dmp xmlns:n1=" <name> DMP_NAME </name> <ipaddress> DMP_IP </ipaddress> <macaddress> DMP_MAC_ADDRESS </macaddress> <description> DMP_DESCRIPTION </description> </n1:dmp> 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 10 of 28

11 Update DMP This API allows you to update a DMP that is already in Digital Signs. PUT /xtas-core/services/dmp/dmps/{id} id: the ID of the dmp you are updating name: the name of the dmp you are adding ipaddress: the ip address of the dmp you are adding macaddress: the mac address of the dmp you are adding description: the description of the dmp you are adding <n1:dmp xmlns:n1=" <id> DMP_ID </id> <name> DMP_NAME </name> <ipaddress> DMP_IP </ipaddress> <macaddress> DMP_MAC_ADDRESS </macaddress> <description> DMP_DESCRIPTION </description> </n1:dmp> Delete DMP This API allows you to delete a DMP from Digital Signs DELETE /xtas-core/services/dmp/dmps/{id} id: the id of the dmp Get DMP process status This API gets the status of the processes running on a DMP. /xtas-core/services/dmp/dmpprocesses/{id} id: the ID of the DMP 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 11 of 28

12 Get DMP settings This API gets all the settings of a DMP /xtas-core/services/dmp/dmpsettings/{id} id: the ID of the dmp Assign configuration parameters to DMP(s) This API sets configuration parameters on DMP(s). PUT /xtas-core/services/dmp/dmpsconfig/ dmpgroupidlist id: the ids of the dmp groups you want the dmps removed from. Valid parameter(s) and value(s) to set and in the correct order <n1:dmpconfigure xmlns:n1=" <dmpidlist> </dmpidlist> <parameters> <id> DMP_ID_1 </id> <id> DMP_ID_2 </id> <nvp> </nvp> <nvp> </nvp> </parameters> </n1:dmpconfigure> <name> MIB_1 </name> <value> MIB_VALUE_1 </value> <name> MIB_2 </name> <value> MIB_VALUE_2 </value> NOTE The values and parameters are defined in the Digital Media Player API documentation Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 12 of 28

13 Publish application to a DMP This API publishes an application to a DMP. POST /xtas-core/api/rest/application/{app_id}/dmp/{dmp_id} app_id: the ID of athe application you want to publish dmp_id: the ID of the dmp you want the application published to <application/> The intended audience for this programmer guide can anticipate and understand the result that this API call returns. Nonetheless, we might document this result in a future revision to this guide. NOTE We do not validate the DMP ID. Therefore, this API will return an HTTP status code 200 OK message even when you pass an DMP ID that is not valid. Please ensure that you pass the <application/> tag, if you do not pass it you will get a 404 Not Found exception Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 13 of 28

14 Content Asset Provisioning Assets in Digital Signs are files that are used to create applications. Assets can not directly be deployed to DMPs. Assets have to be wrapped in applications to be deployed to DMPs. The smallest application that can be deployed to a sign is a single asset inside of a playlist (playlist is an application). These APIs allow for the creation and management of Digital Signs assets. Get Category Tree Assets are organized in hierarchical categories. Each asset can only belong to one category branch. This API is used to identify each category. /xtas-core/services/content/categories/ The intended audience for this programmer guide can anticipate and understand the result that this API call returns. Nonetheless, we might document this result in a future revision to this guide. NOTE In Cisco DMS 5.2, you cannot use this API to add, update or delete asset categories. Get Content Asset List for a Category This API returns a list of the assets in a particular category. /xtas-core/services/content/assets/category/{id} id: the ID of the category 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 14 of 28

15 Upload an Asset This API is used to create a new asset in the Digital Signs media library by uploading a file. Uploading an asset is done through a multi-part form. This multipart form uploads a file with the input name upfile and also the xml with the input name data. POST /xtas-core/services/content/assets/ title: the title for the asset filename: the file s name description: the description of the file filetype: can be FLASH, HTML, IMAGES,UDP, or VIDEO estimatedduration: the default amount of time the asset should stay on screen categoryidlist id: the ID of the category the asset should belong to assetowner: the username of the owner adding the asset This sample HTML file shows how to upload an asset: <html> <body> <form action=" YOUR_HOSTNAME :8080/xTAScore/services/content/assets/" enctype="multipart/form-data" method="post"> File to upload: <input type="file" name="upload_file"/> <br/> data: <textarea cols="40" rows="20" name="data"></textarea> <br/> <input type="submit" value="upload"/> </form> </body> </html> data should be of the XML format: <n1:asset xmlns:n1=" > </n1:asset> <title> ASSET_TITLE </title> <filename> ASSET_FILE_NAME </filename> <description> ASSET_DESCRIPTION </description> <filetype> VALID_FILE_TYPE </filetype> <estimatedduration> <Hours>0</Hours> <Minutes>0</Minutes> <Seconds>0</Seconds> </estimatedduration> <categoryidlist> <id> CATEGORY_ID </id> </categoryidlist> <assetowner> USER_NAME </assetowner> <storagetype>file</storagetype> <downloadurl>true</downloadurl> this API call returns. Nonetheless, we might document this result in a future revision to this guide Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 15 of 28

16 Add Asset from This API is used to create a new asset in the Digital Signs media library from a valid. Uploading an asset is done through a multi-part form. This multipart form only contains an xml with the input name data. POST /xtas-core/services/content/assets/ title: thte title for the asset filename: the url to the file description: the description of the file filetype: can be FLASH, HTML, IMAGES,UDP, or VIDEO estimatedduration: the default amount of time the asset should stay on screen categoryidlist id: the ID of the category the asset should belong to assetowner: the username of the owner adding the asset This sample HTML illustrates how to upload an asset: <body> <html> <form action=" YOUR_HOSTNAME :8080/xTAScore/services/content/assets/" enctype="multipart/form-data" method="post"> data: <textarea cols="40" rows="20" name="data"></textarea> <br/> <input type="submit" value="upload"/> </form> </body> </html> data should be of the xml format: <n1:asset xmlns:n1=" > </n1:asset> <title> ASSET_TITLE </title> <filename> ASSET_FILE_NAME </filename> <description> ASSET_DESCRIPTION </description> <filetype> VALID_FILE_TYPE </filetype> <estimatedduration> <Hours>0</Hours> <Minutes>0</Minutes> <Seconds>0</Seconds> </estimatedduration> <categoryidlist> <id> CATEGORY_ID </id> </categoryidlist> <assetowner> USER_NAME </assetowner> <storagetype>url</storagetype> <downloadurl>true</downloadurl> NOTE Titles must be unique and cannot be blank. Please ensure that your DMM appliance can resolve any that you use the API to pass. Verify that DNS settings are correct in the Application Administration Interface (AAI) command shell Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 16 of 28

17 Get Asset Details This API returns details about a specific asset. /xtas-core/services/content/assets/{id} id: the asset ID Update Asset This API helps you to edit the metadata for a specific asset. POST /xtas-core/services/content/assets/ The asset details should be retrieved first using Get Asset details API above This sample HTML illustrates how to upload an asset: <html> <body> <form action=" YOUR_HOSTNAME :8080/xTAScore/services/content/assets/" enctype="multipart/form-data" method="post"> data: <textarea cols="40" rows="20" name="data"></textarea> <br/><input type="submit" value="upload"/> </form> </body> </html> data should be of the xml format: <n1:editasset xmlns:n1=" agement"> <id> ASSET_ID </id> <assetbasic> <title> ASSET_TITLE </title> <filename> ASSET_FILE_NAME </filename> <description> ASSET_DESCRIPTION </description> <filetype> VALID_FILE_TYPE </filetype> <estimatedduration> <Hours>0</Hours> <Minutes>0</Minutes> <Seconds>0</Seconds> </estimatedduration> <categoryidlist> <id> CATEGORY_ID </id> </categoryidlist> <assetowner> USER_NAME </assetowner> <storagetype> url_or_file </storagetype> <downloadurl>true</downloadurl> </assetbasic> <keepexisting>true</keepexisting> </n1:editasset> 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 17 of 28

18 Delete Asset This API helps you to delete an asset from the media library. DELETE /xtas-core/services/content/assets/{id} id: the asset ID Application Provisioning Applications are the smallest unit in Digital Signs that can be deployed to a DMP or a DMP group. NOTE Except for the Playlist application, DMS 5.2 APIs do not expose the creation or deletion of applications. Get all Applications This API returns a list of all applications. /xtas-core/services/app/apps/ 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 18 of 28

19 Application Provisioning - Playlists A playlist is a Digital Signs application which plays and loops Digital Signs assets. Add a Playlist This API helps you to create a playlist. POST /xtas-core/api/rest/playlist resolution: e.g. 1024X768 randomize: true if the playlist order should be random, otherwise false popenable: true if proof of play should be used on this playlist, otherwise false description: the description of the playlist title: the title of the playlist hours: can be set to 0, or the amount of hours for the asset to stay on screen minutes: can be set to 0, or the amount of minutes for the asset to stay on screen seconds: can be set to 0, or the amount of seconds for the asset to stay on screen assetid: the asset to be used <n2:playlist xmlns:xsi=" xmlns:n2=" ment"> <n2:resolution> RESOLUTION </n2:resolution> <n2:randomize> IS_RANDOMIZED </n2:randomize> <n2:popenable> IS_POP_ENABLED </n2:popenable> <n2:description> DESCRIPTION </n2:description> <n2:owner> USERNAME </n2:owner> <n2:title> TITLE </n2:title> <n2:playlistitems> <n2:item> <n2:plannedduration> <n2:hours> HOURS </n2:hours> <n2:minutes> MINUTES </n2:minutes> <n2:seconds> SECONDS </n2:seconds> </n2:plannedduration> <n2:asset> <n2:assetid> ASSET_ID </n2:assetid> </n2:asset> </n2:item> </n2:playlistitems> </n2:playlist> The intended audience for this programmer guide can anticipate and understand the result that this API call returns. Nonetheless, we might document this result in a future revision to this guide. Get playlist details This API returns information about a particular playlist. /xtas-core/api/rest/playlist/detail/{id} id: the ID of the playlist 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 19 of 28

20 Edit a playlist This API helps you to edit a playlist PUT /xtas-core/api/rest/playlist/{id} id: the ID of the playlist resolution: e.g. 1024X768 randomize: true if the playlist order should be random, otherwise false popenable: true if proof of play should be used on this playlist, otherwise false description: the description of the playlist title: the title of the playlist hours: can be set to 0, or the amount of hours for the asset to stay on screen minutes: can be set to 0, or the amount of minutes for the asset to stay on screen seconds: can be set to 0, or the amount of seconds for the asset to stay on screen assetid: the asset to be used <n2:playlist xmlns:xsi=" xmlns:n2=" <n2:id> PLAYLIST_ID </n2:id> <n2:resolution> RESOLUTION </n2:resolution> <n2:randomize> IS_RANDOMIZED </n2:randomize> <n2:popenable> IS_POP_ENABLED </n2:popenable> <n2:description> DESCRIPTION </n2:description> <n2:owner> USERNAME </n2:owner> <n2:title> TITLE </n2:title> <n2:playlistitems> <n2:item> </n2:item> <n2:plannedduration> <n2:hours> HOURS </n2:hours> <n2:minutes> MINUTES </n2:minutes> <n2:seconds> SECONDS </n2:seconds> </n2:plannedduration> <n2:asset> </n2:asset> </n2:playlistitems> </n2:playlist> <n2:assetid> ASSET_ID </n2:assetid> Delete playlist This API helps you to delete a playlist. DELETE /xtas-core/api/rest/playlist/{id} id: the ID of the playlist 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 20 of 28

21 Insertion and Requestor Provisioning Cisco DMS 5.2 introduces two new concepts: Insertions and Requestors. A Requestor is a named entity that makes use of named Insertions. Insertions are containers for assets. We use information about Requestors and Insertions both, when we generate Proof of Play reports. A note on nomenclature: Insertions and Requestors were previously named Campaigns and Agencies, respectively. While this update in nomenclature is used throughout this document, the API calls themselves still refer to the older terms. Get All Requestors This API returns a list of all named Requestors. /proofofplay_campaign/services/agencies Get Requestor detail This API returns details about a particular Requestor. /proofofplay_campaign/services/agencies/{id} id: the Requestor id Create new Requestor This API helps you to create a new Requestor. POST /proofofplay_campaign/services/agencies name: the name of the Requestor description: the description of the Requestor <ns2:agency xmlns:ns2=" </ns2:agency> <name> OR_NAME </name> <description> OR_DESCRIPTION </description> The intended audience for this programmer guide can anticipate and understand the result that this API call returns. Nonetheless, we might document this result in a future revision to this guide Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 21 of 28

22 Edit Requestor This API helps you to edit the metadata that describes a Requestor. PUT /proofofplay_campaign/services/agencies/{id} id: the ID of the Requestor name: the name of the Requestor description: the description of the Requestor <ns2:agency xmlns:ns2=" </ns2:agency> <name> OR_NAME </name> <description> OR_DESCRIPTION </description> Delete Requestor This API helps you to delete a Requestor. DELETE /proofofplay_campaign/services/agencies/{id} id: the ID of the Requestor Get list of Insertions This API is used to get a list of Insertions /proofofplay_campaign/services/campaigns?start={startvalue}&limit={limitvalu e} Pagination params are optional. If they exist, they should be >= Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 22 of 28

23 Add New Insertion This API is used to add a new Insertion POST /proofofplay_campaign/services/campaigns name: the name of the insertion startdate: the start date of the insertion requestorid: the ID of the Requestor the insertion belongs to resource id: the ID of the application this insertion should track <ns2:campaign xmlns:ns2=" ement"> <name> INSERTION_NAME </name> <description> INSERTION_DESCRIPTION </description> <startdate> START_DATE YYYY-MM-DD </startdate> <enddate> OPTIONAL_END_DATE YYYY-MM-DD </enddate> <agencyid> OR_ID </agencyid> <resources> <resource> <id> APPLICATION_ID </id> <resourcetype>dsm::application</resourcetype> </resource> </resources> </ns2:campaign> Edit Insertion This API is used to update a particular Insertion. PUT /proofofplay_campaign/services/campaigns/{id} insertionid: the ID of the Insertion name: the name of the Insertion startdate: the start date of the Insertion requestorid: the ID of the Requestor the insertion belongs to resource id: the ID of the application this insertion should track 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 23 of 28

24 <ns2:campaign xmlns:ns2=" ement"> <name> INSERTION_NAME </name> <description> INSERTION_DESCRIPTION </description> <startdate> START_DATE YYYY-MM-DD </startdate> <enddate> OPTIONAL_END_DATE YYYY-MM-DD </enddate> <agencyid> OR_ID </agencyid> <resources> <resource> <id> APPLICATION_ID </id> <resourcetype>dsm::application</resourcetype> </resource> </resources> </ns2:campaign> Delete Insertion This API is used to delete a particular Insertion. POST /proofofplay_campaign/services/campaigns/batchdeletion insertionid: the ID of the insertion you want to delete <ns2:campaigndeletion xmlns:ns2=" <id> INSERTION_ID </id> </ns2:campaigndeletion> 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 24 of 28

25 Proof of Play Proof of Play APIs allow you to generate reports for each Insertion. Get Insertion summary reports This API returns a summary report for a particular Insertion. /proofofplay_core/services/reports/error/campaign/{id}/fromdate/{yyyymm DD}/toDate/{YYYYMMDD}/ id: Insertion id fromdate: desired start date of the report todate: desired end date of the report Get Insertion success reports This API returns a success report for a particular Insertion. /proofofplay_core/services/reports/success/campaign/{id}/fromdate/{yyyy MMDD}/toDate/{YYYYMMDD}/ id: insertion id fromdate: desired start date of the report todate: desired end date of the report Get Insertion error reports This API returns an error report for a particular Insertion. /proofofplay_core/services/reports/success/campaign/{id}/fromdate/{yyyy MMDD}/toDate/{YYYYMMDD}/ id: insertion id fromdate: desired start date of the report todate: desired end date of the report 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 25 of 28

26 Schedule Provisioning These APIs help you see future deployments of applications to DMPs. Get all applications scheduled for a date This API returns a list of all applications that are scheduled to deploy on a given date. ATTENTION This API requires media type to be set to text/xml NOT application/xml /xtas-core/api/rest/scheduler/schedule/date/{yyyy-mm-dd} date: the date for which you d like to get the schedule 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 26 of 28

27 Emergency These APIs help you to override the saved schedule and publish an emergency application to a group of DMPs. Start Emergency Messaging This API starts the emergency. POST /xtas-core/api/rest/emergency/start emergencyapplication id: the ID of the application to use as an emergency group id: the ID of the group to which the emergency application applies <singleemergencystart xsi:nonamespaceschemalocation=" i/emergency.xsd" xmlns:xsi=" <emergencyapplication id=" APPLICATION_ID "> <grouplist> <group id=" DMP_GROUP_ID "/> </grouplist> </emergencyapplication> </singleemergencystart> Stop Emergency messaging This API stops the emergency. POST /xtas-core/api/rest/emergency/stop group id: the ID of the group to which the emergency application applies <singleemergencystop> <grouplist> <group id=" DMP_GROUP_ID "/> </grouplist> </singleemergencystop> 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 27 of 28

28 Printed in USA CXX-XXXXXX-XX 01/ Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 28 of 28