Channel reporting APIs 1.5.1 has been released and is now in production. This maintenance release contains a fix for handling the reporting of deleted webcasts. For more details of the changes please see the change history (release notes) in the appendix of the updated reporting API technical specification. If you believe you’re experiencing any issues in relation to this new release, please email support@brighttalk.com. …
Channel reporting APIs Release 1.5.0 – GA
We’re pleased to announce that release 1.5.0 of the Channel reporting APIs are now live. For more details of the changes which have been made to the APIs please see the change history (release notes) in the appendix of the updated reporting API technical specification. If you believe you’re experiencing any issues in relation to this new release, please email support@brighttalk.com. …
Channel reporting APIs Release 1.5.0 – Release Candidate
A release candidate for release 1.5.0 of the Channel owner reporting APIs is now available for customer testing in the BrightTALK staging environment. This release adds new APIs for reporting on your webcast attachments and their accesses by your audience. Details can be found in the updated reporting API technical specification, in sections Webcast Attachment APIs and Subscriber Webcast Attachment …
Channel reporting APIs Release 1.4.0 – GA
We’re pleased to announce that release 1.4.0 of the Channel reporting APIs is now live. For more details of the changes which have been made to the APIs please see the change history (release notes) in the appendix of the reporting API technical specification. If you believe you’re experiencing any issues in relation to this new release, please email support@brighttalk.com. Thanks, …
Channel reporting APIs Release 1.4.0 – Release Candidate
A release candidate for release 1.4.0 of the Channel owner reporting APIs is now available for customer testing in the BrightTALK staging environment. This new release extends the data reported for channel subscribers and subscriber webcast activity to include a few additional fields. More details can be found in the updated reporting API technical specification.