Livestream API
Livestream docs now describe access as whitelisted apps, not Enterprise-plan exclusivity.
/livestream-api/getting-started: Prerequisites now require a whitelisted app. The access step no longer mentions Enterprise enablement or asking an account team. The RTMP encoder example is now ffmpeg or similar./livestream-api/authentication: OAuth 2.0 and OAuth 1.0a requirements now say the app must be whitelisted for the Livestream API./livestream-api/scheduled-broadcasts/overview: Scheduling endpoints are documented as available to whitelisted apps./livestream-api/introduction: The Get started card now points to prerequisites, access, and credentials./forms/livestream-api-access: The access form note now says access is limited to whitelisted apps and subject to review.
Request access via the Livestream API Access Form.
X API v2 — Batch compliance
Upload size and job-prep guidance on batch compliance is updated.
/x-api/compliance/batch-compliance/integrate: A singlePUTis documented as up to 128 MB (about 6.5 million IDs), not 1 GiB. The413error text matches that limit. Docs now recommend grouping IDs from a similar time period in the same job for faster processing./x-api/compliance/batch-compliance/quickstart: The sample data file limit is now 128 MB.