Velveteen API Endpoints
Updated August 27, 2026
The Velveteen API exposes scoped endpoints for releases, artists, tracks, labels, people, publishing houses, pitches, and royalties. List endpoints use pagination, while unsuccessful requests return standard HTTP status codes and a concise error message. Your API key and scopes determine which records and operations a request can access.
Here is what the API reaches and how responses are shaped. The Documentation tab has the exact paths and fields.
Resource groups
Catalog
Releases, artists, tracks, labels, people, and publishing houses.
Pitches
List, read, create, update, and withdraw pitches.
Royalties
Read balance and earnings, and request payouts.
Pagination and errors
List endpoints take page and page-size parameters and return a total count, so you can page through results.
Errors use standard status codes: unauthorized for a bad key, forbidden for a missing scope or plan, not found for a missing resource, conflict when a delete is blocked by a dependency, and bad request for invalid input.
Tip
Frequently asked questions
What can the API manage?+
Releases, artists, tracks, labels, people, publishing houses, pitches, and royalties.
How does pagination work?+
List endpoints accept page and page-size parameters and return a total count.
Why did a delete return a conflict?+
Deletes are blocked when a dependency exists, such as a non-draft release or an active pitch.
Where are the exact paths and fields?+
In the Developer Documentation tab, which lists every endpoint, its scope, parameters, and response.
Related articles
Authentication
The base URL, the Authorization Bearer header with your key, and where to find the in-app reference and code examples.
Scopes
The six scopes, catalog, pitches, and royalties in read and write form, and how they limit what a key can do.
Overview
Build on Velveteen: API keys, Bearer authentication, scopes, and the catalog, pitching, and royalty endpoints. Available on the Pro and Label plans.