Music Delivery
Send a release as one accountable package: structured metadata, declared masters, artwork, identifiers, territories and explicit rights instructions. Kasty preserves the delivered source and exposes validation, upload, processing and issue state separately.
Current availability
| Channel | Current availability | Activation boundary |
|---|---|---|
| Partner Console | AVAILABLE | Approved organization and current agreement; sender and write cohort are activated separately. |
| Folder | LIMITED PILOT | Canonical package and manifest through the guided bulk-delivery pilot. |
| CSV / JSON | LIMITED PILOT | Structured adapters normalize into the canonical manifest during guided onboarding. |
| Direct API | LIMITED PILOT | Approved organization, current agreement, scoped credential, active sender and enabled write cohort. |
| ZIP | UNAVAILABLE | Unavailable until bounded staging, archive inspection and malicious-archive controls are production-ready. |
| DDEX ERN | BILATERAL ONBOARDING | Agreed DDEX rights, DPID identities, ERN profile, choreography, transport, mappings and conformance. |
One canonical pipeline
Partner Console, guided bulk adapters and Direct API normalize into kasty.music.delivery.v1. They use the same validation, object-scoped uploads, durable jobs, issue codes, rights evidence and append-only revisions. DDEX is a bilateral adapter into that model, not a bypass.
Choose the next step
- Use the quickstart for one complete release.
- Compare delivery channels before designing an integration.
- Read authentication and credentials and scopes before creating machine access.
- Inspect errors before implementing retries.
- Review the generated API reference.