DEVELOPER RESOURCES
API access is now part of the developer platform.
API access now requires a developer API key and a paid developer plan. Migrate from the retired public reference API to the Tunings developer API.
Build with the Tunings engine
Upgrade to Tunings Pro for catalog lookups, custom fretboards, scale mapping, chord positions, and transposition.
Migrating an integration
The old tunings.io/api/v1/* routes return 410 API_RETIRED and no catalog data. Requests are not redirected, and keys are not forwarded between hosts.
Use https://api.tunings.io/v1 with an Authorization Bearer key. The developer API has its own IDs, request schemas, pagination, and response format; this is not a drop-in URL replacement. Review the OpenAPI specification before migrating. Legacy relationship routes do not have direct equivalents in V1.
Access and subscriptions
Live music endpoints require an active paid-tier developer plan and a valid API key. Tunings Pro includes the app, REST API, and MCP tools for $19.99 USD/month plus applicable tax. Upgrade and create your key from the Developer page in your account.
The public reference library remains available for reading and learning. API health and documentation remain public.