Compatibility and boundaries

Know what to expect from v1.

v1 reuses the app's ownership, billing, validation and publishing pipeline. Additive response fields are compatible; breaking contracts require a new version. OAuth connection, billing changes, key management and account deletion stay in the app. Media upload and outbound webhooks are not part of v1; poll status. Existing uploaded media IDs may be referenced when owned and ready. Bearer CORS is supported without cookies; keep permanent keys on your server.