Changelog

v1.6 — Current

August 7, 2026

Generation certificates. Every completed track and sound effect on a paid plan now has a downloadable PDF generation certificate — a formal, single-page document issued by Riku AI LLC confirming the work was generated by you on Finetuning, with your prompt, settings, and the AI model. Finetuning claims no ownership of generated works; all rights stay with the creator. Two new endpoints return the PDF binary:
- GET /v1/generations/:id/license — certificate for a music or instrumental track
- GET /v1/sound-effects/:id/license — certificate for a sound effect
Public certificate verification. Every certificate carries a permanent number and a public verification page at https://finetuning.ai/verify/<number> — anyone can confirm it, no account or API key needed.

Certificate downloads use the blanket 60/min/user read limit. The certificate number and issue date are permanent — repeat downloads return the same certificate, and renaming a track refreshes the PDF on the next download without changing its number.
Certificates require a Plus, Pro, or Lifetime plan (PAID_PLAN_REQUIRED on free accounts) and a completed work (NOT_READY otherwise).

July 2, 2026

Zapier: instrumental & sound-effect generation. The Zapier integration gained two actions — Create Instrumental Track and Create Sound Effect — plus a Find Sound Effect by ID search to fetch the finished clip. The New Completed Track trigger fires for instrumental tracks too (they share the music library).

No API changes in this release — the Zapier actions wrap the existing POST /v1/instrumental and POST /v1/sound-effects endpoints.

June 25, 2026

Instrumental generation is now on the API. POST /v1/instrumental creates a vocal-free track from a plain text description — the model picks the instrumentation and tempo, so there's no BPM, key, scale, or time signature to set. Instrumentals draw from the same monthly credit pool as music.
type filter and field on generations reads. GET /v1/generations accepts ?type=music or ?type=instrumental, and both the list and detail responses now include a type field. Instrumental tracks live in the same store as music — there is no GET /v1/instrumental.
ft CLI gained instrumental and sound-effect commands. ft instrumental (alias ft inst) generates a track and reuses ft get / ft download / ft list --type instrumental for reads. The new ft sfx group (generate, list, get, download) covers sound effects. See the command reference.

Each create endpoint — music, instrumental, and sound effects — has its own 10/min/user burst limit (GENERATION_RATE_LIMITED). Reads stay on 60/min/user.
When read back, an instrumental track's parameters.bpm, parameters.keyscale, and parameters.timesignature are null; duration and seed are present.

Sound effects are now on the API. Generate short AI sound effects (1–8 s) with three new endpoints:
- POST /v1/sound-effects — generate a sound effect
- GET /v1/sound-effects — list your sound effects
- GET /v1/sound-effects/:id — get one sound effect (poll for completion)
POST /v1/sound-effects accepts an optional webhook URL — we POST the finished (or failed) clip to your endpoint, just like music. See Webhooks.

Sound effects are metered by a shared daily cap of 100 per UTC day — API and web-app generations draw from the same pool. Every create response returns dailyRemaining; exceeding it returns DAILY_LIMIT_REACHED. See Rate Limits.
Creation has its own burst limit of 10/min/user (GENERATION_RATE_LIMITED), separate from music. Reads stay on the 60/min/user limit.
Sound effects carry no musical parameters, so the webhook payload's parameters field is null for SFX.

Bulk track deletion. POST /v1/generations/bulk-delete permanently deletes up to 100 tracks in one request, with per-item success/error reporting. See Bulk delete.
Playlists are now on the API. Five new endpoints:
- GET /v1/playlists — list your playlists
- GET /v1/playlists/:id — get a playlist with its tracks
- POST /v1/playlists/:id/tracks — add up to 100 tracks
- POST /v1/playlists/:id/tracks/bulk-remove — remove up to 100 tracks
- POST /v1/playlists/:id/tracks/move — move up to 100 tracks to another playlist
All bulk endpoints share the same model: 100 IDs max per request, partial success (one bad ID doesn't fail the batch), and a per-item errors array. New error codes ADD_FAILED and MOVE_FAILED are returned when zero items in a batch succeed. See Errors.

Playlist privacy rules are enforced server-side: public playlists may only contain public tracks, and private playlists may only contain your own tracks. The API never changes a track's visibility for you.
A bulk request counts as one request against the 60/min rate limit, regardless of how many IDs it carries.
The ft CLI supports all five endpoints: ft delete, ft playlists, and ft playlist add / remove / move. See the command reference.

Zapier integration (private beta). Connect Finetuning to 8,000+ apps — auto-generate tracks and route finished MP3s anywhere, no code. See Zapier.
POST /v1/generations accepts a webhook URL — we POST the completed (or failed) track to your endpoint, so you don't have to poll. See Webhooks.
tags maximum increased from 500 → 700 characters.
duration range widened from 10–180 → 5–210 seconds (free tier remains capped at 120).

POST /v1/generations now returns 202 Accepted (previously 201 Created).
Rate limiting on POST /v1/generations is now reported separately as GENERATION_RATE_LIMITED (10/min/user); RATE_LIMITED continues to cover read endpoints (60/min/user). See Rate Limits.

Base URL: https://pub.finetuning.ai

More endpoints and features are coming soon — stay tuned!