Step 1: Share Your Information
Before your onboarding can begin, your Netflix contact will need the following from you:
User Access: Names and email addresses of anyone who needs access to the API and its documentation.
Key Delivery: A primary contact email to receive your test NetKey.
Delivery Mode: Your chosen asset delivery method (see your Netflix contact for a comparison of the three transfer modes).
Account Identifiers: Vendor name and Vendor ID.
Localization Base: Primary country and language (e.g., US / English).
Timeline: Planned launch date.
Step 2 - AWS / S3 Setup (if delivering via S3)
If you're delivering content via S3, provide Netflix with the ARN of your AWS role - the role your system will use to upload content to Netflix's S3 bucket.
Role Provisions: Example format: arn:aws:iam::[yourAccountId]:role/[yourRoleName]
IAM Alignment: Once Netflix sets up the corresponding IAM role, you'll need to update your AWS role to assume Netflix's IAM role in both test and production environments.
Step 3 - Test Environment Access
Once your account is provisioned, you'll receive a NetKey via secure message. Every API call requires a bearer token - include it in the Authorization header on every request like this:
Step 4 - Integration Testing
Once you have access, the core delivery loop is:
Submit Title: Submit a title via POST /v1/ingest
Check Status: Check the Reporting API (/v1/titleDetails or /v1/requiredActions) for any outstanding actions.
Resolve Conflicts: Resubmit to resolve those actions.
Iterate: Repeat until the title reaches COMPLETED.
nClearance: Your Netflix contact will confirm when you're cleared to move to production.
Step 5 - Production Setup
For production, you'll create your own NetKey directly rather than receiving one from Netflix. Additional documentation and resources will be shared with you by your Netflix contact to guide you through the process.