Downloading session recordings

[aaron.gidusko]

What is the easiest way to programmatically download recordings of WebEx sessions?

I have found a number of confusing API documents. Could someone kindly direct me to the most current documentation for downloading or exporting WebEx sessions?

[nmorrow · Accepted solution]

Hello,

     Download of NBR files is best done with a combination of XML API and

NBR API. XML API request ep.LstRecording will give you the original meeting topic, host username, meeting date and time, and recording ID, among other information. ep.DelRecording will allow you to delete recordings after download. NBR API request NBRFileOpenService.downloadFile will download the recording by binary SOAP attachment in a multipart HTTPS transaction. LstRecording does also provide a file URL for manual download via web browser, it may be possible to automate that process instead of using NBR API, but it is not a direct link and you will be met with javascript redirects and possibly HTTP status redirects or header redirects as well. NBR API Service URL must be requested by contacting webex-meetings-api-dev@cisco.com and providing your WebEx site URL with your request for NBR API Service URL, as it cannot be inferred by any means available to end users. You may find also find the schema that contains the downloadFile request once you receive your NBR API Service URL, using the format https://nxx1wss.webex.com/nbr/services/NBRFileOpenService?wsdl, where "nxx1wss" should be replaced by the actual subdomain that is provided when requested.

[emma.nendza]

Thanks for the instructions.  I am having a problem when attempting to add a Web Reference to the WSDL that you provided.  I replaced nxx1wss with the URL that was provided to me and I get this error:

MSDiscoCodeGenerator failed.  Unable to import binding NBRFileOpenServiceSoapBinding from namespace

http://[myURL]/nbr/services/NBRFileOpenService

I am using Visual Studio 2017 for c#

[nmorrow]

Hello,

     WebEx API services are built in JAVA, and the schemas are generated by the JAVA platform. .Net usually has trouble importing the schemas due to some differences in available objects types, there may be some additional details in your error output that points to specific objects or definitions. You'll need to hard code your API request in this case, as we will not be able to modify the published schema due to backward compatibility promises with existing code.

[Shivang]

with nbr API i am getting the following error
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>WSS1002: WebEx11 Site Is Not Supported</faultstring>
<faultactor>NBRStorageLocalService</faultactor>
<detail>
<ns1:exceptionName xmlns:ns1="http://xml.apache.org/axis/">com.webex.webservice.nbr.xmlhelper.NBRException</ns1:exceptionName>
<ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">nsj1wss227.webex.com</ns2:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>