Dynamic Ingest API: Best Practices

Introduction

The Dynamic Ingest API is powerful and flexible, but to use it most effectively, you need to follow some best practices, which are detailed below.

Best practices

Below are rules and guidelines for Dynamic Ingest.

• The profile field for ingest requests is optional. Avoid hard-coding the profile in apps and integrations - instead, set the most commonly used profile as the default for the account and omit the field, or fetch the available profiles for the account and force the user to choose one.
• No more than 10 requests per minute on the same video are allowed.
• You should not have duplicate jobs processing for the same video, though ingesting other assets, such as images and text tracks, along with the video in the same job is fine.

  if you are using an automated process for creating ingestion jobs that could potentially create multiple jobs on the same video ID, you need to check notifications to ensure that there are no other jobs processing on the same video before creating a new one.

• A 20 request-per-second limit on each account for total requests across Dynamic Ingest and the CMS API.
• Each account supports up to 1,000 concurrent ingest jobs and up to 3,000 ingest job submissions per minute. If you go over these limits, the additional jobs are queued and processed as soon as possible. There is no need to throttle large batches or migrations manually.
• For large batches or migrations, use notifications to track when each job completes. A queued job shows the status pending in the CMS API, the same as a job that is processing.
• There is no file size limit for the ingested content, but there is a duration limit of 24 hours for videos.
• Validate your ingest profile changes to ensure you are getting the results you want before ingesting full batches.