Skip to Content
WorkflowsShare a creation

Share a creation

User activity

Make a creation public

The Studio submits a PATCH to /api/ngamia/v1/music/creations/{id} with JSON { "is_public": true }. The proxy forwards the method, body, content type, and session bearer token. On success, the web app updates the creation locally and copies a URL of the form https://app.ngamia.com/share/{id} when requested.

Making a track public can expose both the audio and its prompt. The web interface tells the owner that the prompt is included. The upstream API decides whether the update succeeds and how visibility is persisted.

Public share page reads

The web share page calls GET /api/ngamia/v1/music/public/{id} for metadata and GET /api/ngamia/v1/music/public/{id}/content for audio. These are the only unauthenticated proxy shapes. The share page expects metadata with id, prompt, model, duration_ms, is_public, and created_at properties; that is a consumer expectation, not validation performed by this proxy.

If metadata or audio cannot be retrieved, show a not found/private state from the upstream response. Do not assume that possessing a creation ID makes the track public.

Last updated on