Who this key is
Authorization
ApiKeyAuth API key from API Keys in the dashboard menu.
In: header
Response Body
application/json
application/json
curl -X GET "https://example.com/api/v1/me"{ "team": { "id": "cm4tmz0q10000js04h1f2x8gh", "name": "Acme" }, "organization": { "id": "cm4tmz0q10000js04zzzzzzzz", "name": "Acme Inc", "slug": "acme" }, "api_key": { "name": "Zapier" }, "label": "Acme (Zapier)", "self": "https://automette.com/api/v1/me"}Read a reference page GET
One page in full, as Markdown in the `content` field. Send `Accept: text/markdown` to get the body on its own with no JSON envelope, which is usually what you want to drop into a model's context. Only fonts we ship can be used, and only assets uploaded to the template resolve: both are covered here, and both are the most common way a first render fails.
Where to start GET
The entry point. One call that says what this API is for and where to read the rest. `start_here` points at the **recipes** skill: what you can do and the route to each thing, including what is deliberately not possible. Read it before authoring anything: it is the difference between a template that renders and one that looks plausible and fails. `skills` is the full catalogue, each fetchable in full at its `self`.