Provider readinessInterfaces and provider certification may evolve. Check account capabilities before production use.Read the readiness contract

Prepare large videos for publishing

Design upload, processing, scheduling, and failure handling for long-running video media.

Direct answer

Upload video early, complete the asset, and wait for processing before the scheduled dispatch window. Use provider capabilities to validate duration, dimensions, aspect ratio, container, codec, thumbnail, and platform-specific metadata before a post reaches review.

What this means in practice

Upload video early, complete the asset, and wait for processing before the scheduled dispatch window. Use provider capabilities to validate duration, dimensions, aspect ratio, container, codec, thumbnail, and platform-specific metadata before a post reaches review.

Use the documented brand and account boundaries consistently across the scheduler, REST API, SDK, MCP tools, SSE consumers, and webhooks. That makes the same social operation explainable to an operator and reproducible by an integration.

Implementation checklist

  1. Collect file size and media metadata before upload.

  2. Use direct upload and a resumable client strategy where supported by the upload URL.

  3. Wait for processing or transcoding completion before final approval.

  4. Preview each video target because platform formats differ materially.

  5. Schedule with enough lead time to absorb processing and provider ingestion latency.

Operational details

A delivery containing video uses the video credit rate only when provider success is confirmed.

Provider processing can continue after App9 Post uploads successfully; result reconciliation records that transition.

Thumbnail support is capability-dependent and may differ by account or video surface.

Common mistakes to avoid

Protect intent, tenant boundaries, and provider state.
  • Do not schedule a large upload for the same minute it finishes transferring.
  • Do not assume one transcode satisfies every network's current limits.
  • Do not retry an ambiguous provider response without checking for a remote external ID.

Was this useful? This documentation is reviewed against the public App9 Post contract. Use the API reference and live capability response for machine-enforced details.

Open API reference