Ingest API Workflow Guidelines

General overview

The Ingest API is an alternative to the MIP (Media Ingest Portal) designed for distributors who need to automate the delivery of large batches of content into Paramount’s Media Supply Chain. Instead of manually uploading through the portal, distributors will programmatically move media and register it via API calls. Please see detailed documentation for Ingest API Workflow here.

API Onboarding & Setup

Before anything can be delivered, the distributor must be onboarded. This involves setting up Aspera (Paramount’s accelerated file transfer mechanism) so the distributor can push content into Paramount’s AWS S3 ingest bucket. Additionally, an API token will be generated by Paramount’s Media Ingest Management team to authenticate the calls. See detailed
documentation for Aspera setup here.

Delivery Workflow

  1. File Transfer via Aspera: The distributor moves their media files into Paramount’s S3 bucket using Aspera. They can do this via Aspera Connect, HTTP Gateway, or Aspera Transfer SDK. This is the physical file movement step.
  2. API Call to Register the Material: Once the file is in the bucket, the distributor makes a POST call to the ingest endpoint (http://mediaingestapi.paramountmsc.com/material/metadata/ingest), passing a request body that includes:
    1. The Edit CRID — the unique anchor ID that ties the materials to the correct title/edit in our repository. This will be provided by the Paramount GMC Onboarding Team in advance.
    2. Technical metadata about the material (content type, format details, etc.)
    3. An uploader email address (to receive metadata failure notifications)
    4. A sourceSystem field identifying the distributor (e.g., “API – Paramount Pictures”)

One API call is made per unique material. Multiple assets under different EditCRIDs require separate calls.

  1. API Response Paramount’s system immediately returns a response code:
    1. 200 — request received successfully, processing will proceed
    2. 400 — malformed request or missing/unsupported data
    3. 403 — invalid authentication token
    4. 500 — infrastructure issue on Paramount’s side
  2. Processing in the Media Supply Chain: Once accepted, the material enters Paramount’s ingest workflow — it gets validated, normalized, and accepted into the Media Supply Chain.

If you are interested in utilizing the Ingest API, please reach out to the Technical Onboarding Team at migtechnicalonboarding@paramount.com for more information.

Copyright © 2026 Paramount

Scroll to Top