tencent cloud

Video on Demand

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Product Features
Features
Strengths
Scenarios
Solutions
Professional Edition
Introduction to Video On Demand Professional Edition
Quick Start
Console Guide
Development Guide
Purchase Guide
Billing Overview
Billing Modes
Purchase Guide
Viewing Bills
Renewal
Overdue Policy
Refund Policy
Getting Started
Console Guide
Console Overview
Service Overview
Application Management
Media Management
Package Management
License Management
Real-Time Log Analysis
Practical Tutorial
Media Upload
Smart Cold Storage of VOD Media Asset Files
Video Processing
Distribution and Playback
How to Receive Event Notification
How to Migrate Files from Origin Server to VOD
Live Recording
How to Pull from Custom Origin Servers
How to Use EdgeOne to Distribute Content in VOD
Development Guide
Media Upload
Media Processing
Video AI
Event Notification
Video Playback
Media Encryption and Copyright Protection
Broadcast Channel
CAM
Media File Download
Subapplication System
Error Codes
Player SDK
Overview
Basic Concepts
Features
Free Demo
Free Trial License
Purchase Guide
SDK Download
Licenses
Player Guide
Integration (UI Included)
Integration (No UI)
Advanced Features
API Documentation
Player Adapter
Player SDK Policy
Server APIs
History
Introduction
API Category
Other APIs
Media Processing APIs
Task Management APIs
Media Upload APIs
Media Management APIs
Event Notification Relevant API
Media Categorization APIs
Domain Name Management APIs
Distribution APIs
AI-based Sample Management APIs
Region Management APIs
Data Statistics APIs
Carousel-Related APIs
Just In Time Transcode APIs
No longer recommended APIs
Making API Requests
AI-based image processing APIs
Parameter Template APIs
Task Flow APIs
Data Types
Error Codes
Video on Demand API 2024-07-18
FAQs
Mobile Playback
Fees
Video Upload
Video Publishing
Video Playback
Web Playback
Full Screen Playback
Statistics
Access Management
Cold Storage
Agreements
Service Level Agreement
VOD Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Overview

PDF
Focus Mode
Font Size
Last updated: 2022-10-27 12:14:59
An operation such as uploading, deleting, or video processing initiated on a video in VOD can be referred to as an event. The execution of an event takes a certain amount of time. Upon completion of the event, VOD will immediately notify the application service of the execution result, i.e., sending an event notification.
VOD supports the following types of event notifications:

Event notification modes include "normal callback" and "reliable callback". You can log in to the VOD Console to set the callback mode and select the events for which you want to receive callbacks. For detailed directions, please see Callback Settings.
Normal callback: configure a callback URL in the console. After an event is completed, the system will send an HTTP request to this URL, which contains the notification content.
Reliable callback: after an event is completed, the VOD system will put the notifications into a built-in message queue, and then the application service will consume the notifications in the queue through a server API.

Normal Callback

Normal callback is a mode in which the application service passively receives event notifications. After the callback URL is configured and the normal callback mode is selected, VOD will initiate a callback to the callback URL after an event is completed.
A normal callback initiated by VOD is an HTTP request, where the request body is in JSON format and the content is the EventContent structure excluding the EventHandle parameter. Take task status change notification as an example. The EventType parameter in the callback is ProcedureStateChanged, and the information is represented by the ProcedureStateChangeEvent parameter (ProcedureTask structure).

Reliable Callback

Reliable callback is a mode in which the application service actively pulls event notifications to VOD. After the reliable callback mode is selected, the VOD system will put event notifications into a queue, and the application service will consume the notifications in the queue through a server API. After the application service gets a message through the PullEvents API, the ConfirmEvents API needs to be called for confirmation. The message must be confirmed for receipt before it can be removed from the queue in VOD, so the reliability of "reliable callback" is higher than that of "normal callback". If the requirement for event notification reliability is high, you are recommended to use the "reliable callback" mode.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback