Validation

Validate a complete business manifest before creating a batch. The dry run uses the same strict parser and policy resolution as submission without writing catalog state.

Dry run

Call validateMusicDelivery. A valid response can include the normalized manifest hash and exact account, sender, territory and video-use binding needed for a versioned rights declaration.

Blocking errors

Blocking issues must be fixed before submission. They identify the affected entity, stable code, JSON path and suggested action. Authentication, agreement and quota responses remain HTTP-level actions rather than being converted into metadata errors.

Warnings

Warnings describe reviewable risk that does not necessarily prevent durable acceptance. Treat warning policy as versioned service behavior; do not ignore all warnings by default in automation.

JSON paths

Use the supplied JSON path to place an error next to the exact row or field in a Partner UI. Branch on stable code, not mutable English text. See Issues and Errors.