Tiled’s HTTP API follows the OpenAPI v3 specification. Additionally, it follows the JSON API standard.

When Tiled is configured to use an Authenticator, it adds routes that comply with the OAuth2 protocol. Specifically, it implements “sliding sessions” with access and refresh tokens that are JWTs. See Security for an overview and Authentication Details for details.


The routes are generally spelled like GET /api/v1/{action}/{path}/, like GitHub repository URLs, with the path following the structure of the Tree entries.

The GET /api/v1/metadata/{path} route provides the metadata about one node. The GET /api/v1/search/{path} route provides paginated access to the children of a given node, with optional filtering (search). The responses contain links to the data, in various forms.

For example, data access routes GET /api/v1/array/block/{path}, GET /api/v1/array/full/{path}, and GET /api/v1/table/partition/{path} provide options for slicing and sub-selection specific to arrays and tables. Generic clients, like a web browser, should use the “full” routes, which send the entire (sliced) result in one response. More sophisticated clients with some knowledge of Tiled may use the other routes, which enable parallel chunk-based access.

The GET /api/v1/container/full/{path} route provides all the metadata and data below a given directory. This route also works for other container-like data structures.

The root route, GET /api/v1/ provides general information about the server and the formats and authentication providers it supports.

Depending on the server configuration, there may be authentication-related routes nested under /api/v1/auth/.


To view and try the interactive docs, visit

or, to work fully locally, start the Tiled server with the demo Tree from a Terminal

tiled serve demo

and navigate your browser to http://localhost:8000/docs.