This is a basic level API training, aimed for developers for introducing the Kaltura, backend terminology, and building blocks of the API services & actions. Covering what is the KS and why is it needed? As well as understanding where and how can the trainee test their own API calls.
Objectives
Get to know the fundamentals of the API servers & client's workflow.
Understand the building blocks of the API (services && actions).
Understand what is the KS and why is it needed.
Get to know some of Kaltura's most common actions, data, and workflows.
Agenda
Topic
Instruction:
Greeting/ Introduction
What is the API and why it is needed?
Understanding the different use cases you would like to achieve, ie, Upload, Notification Handling, Metadata Updating, Other.
Understanding the building blocks of the API (services && actions)
Review of the backend servers & clients.
Explore the knowledge hubs.
Kaltura client libraries and where can they be downloaded from.
Why use a client library over pingable URLs?
Understanding the Kaltura Session
What is the Kaltura security model?
What is the KS and why is it needed?
What are the security considerations when generating a KS?
Hands-on
Learn the workflow process on how to create an API call.
Learn further actions we can take once our KS session is set.
Kaltura entities
What are entries?
What is the entry creation process?
What are categories?
Metadata
What is custom metadata and why is it needed to overload metadata on the entry-level?
How can access to entries be limited (access control and scheduling)?
Upload
How can a large number of entries be created in minimal time (bulk upload)
How can API calls be stacked together to conserve resources?
What is the difference between dynamic thumbnails and thumbnail assets?
Manage Notifications
How can server notifications be used to help the customer with their own integration with the API?