A filament suspension bridge spanning a dark glowing valley

Working in one call.

A key, a POST, a poll.

quickstart

The whole request, end to end

Authenticate with a bearer key, post a brief, poll the task. Everything below is the whole integration — no SDK, no webhook to host. The full field list lives in the API reference.

See what comes back → fields, example payload, and how polling ends.

Every call goes to api.glidingnote.ai over TLS with a bearer key issued to your workspace; audio is served from cdn.glidingnote.ai. We run the gateway, so keys, rate limits and usage all belong to your Gliding Note account.

# 1 · authenticate with a bearer key (server side only) curl -X POST https://api.glidingnote.ai/v1/tracks \ -H "Authorization: Bearer $GLIDINGNOTE_KEY" \ -H "Content-Type: application/json" \ -d '{ "prompt": "warm house, 122 bpm, loop-safe, no vocals", "tier": "commercial", "length_s": 74, "stems": false }' # 2 · the reply is a task you can poll { "task_id": "tsk_8f21c0a4", "status": "queued", "poll_url": "/v1/tasks/tsk_8f21c0a4" } # 3 · poll until the status is succeeded GET /v1/tasks/tsk_8f21c0a4 { "status": "succeeded", "audio_url": "https://cdn.glidingnote.ai/…/master.wav", "licence": { "tier": "commercial", "code": "AUR7L2610632-2C9F-…" } }

keys

Keys are per workspace

Create one in the dashboard; it is shown once. Keep it server-side — a key in the browser is a key in someone else's browser.

errors

Failures are explicit

4xx means your request is wrong and retrying will not help; 5xx and 429 are safe to retry with the same task reference.

limits

Rate limits per key

Polling has a separate, higher allowance than generation. A batch of ten items is one request, not ten. Credits are reserved before a call and released on failure, so a key can never spend past its quota.