Developers

tabs.garden developer portal

Build agent and developer integrations with the public tabs.garden song index, tab JSON API, OpenAPI specification, and crawlable documentation.

Quickstart

The tabs.garden public API is read-only and does not require an API key for public song and tab discovery. Start by fetching /api/songs, choose a song, then remove the .json suffix from its file value and request /api/tabs/{tabKey}. Responses are JSON and are designed to be cacheable, scriptable, and compatible with function-calling tools through the published OpenAPI document.

curl https://tabs.garden/api/songs
curl https://tabs.garden/api/tabs/00814157f74da78d62589eaef90a628f757dd5c59ae6eff9642b288c90328cd6

Public endpoints are suitable for search tools, music education projects, and agents that need canonical song-page links. Administrative routes used to import, edit, or delete content are private and require a bearer token that is not issued through this portal. If you need a sandbox, mirror the public API with a local static data set from the repository or use the production read endpoints with normal HTTP caching.