API

The OneTake Studio read-only REST API for pulling your inventory, maintenance, and valuation data into other tools.

The OneTake Studio API is a read-only REST API that lets you pull your inventory, maintenance, and valuation data into accounting software, BI tools, and automations like Zapier.

Coming soon. The public API is rolling out as a Pro plan feature and isn't generally available yet. This reference describes the v1 (read-only) API. When it ships, API access will require a Pro plan (it won't be available on the trial) — see Membership → Plans.

Base URL

https://api.onetakeapp.com/v1

All endpoints return JSON and require a bearer token.

What you can do

Read your inventory — list items and fetch full item detail, including photos and valuation state.
Read locations — list your studio's locations (Studio plan).
Read maintenance — scheduled and completed maintenance per item.
Read policies — list active insurance policies and fetch full policy detail, including assignment count.
Read policy assignments — see which policies an item is assigned to and what value is declared under each.
Read account info — your plan tier, current period, and item count.
Sync efficiently — every list endpoint supports ?updated_since= so you only pull what changed.

Zapier and no-code tools

The API works with Zapier and similar no-code platforms as-is — no OAuth required. Authenticate with a Personal Access Token as the bearer credential, the same way any other integration does.

Two patterns cover most Zapier use cases:

"Updated item" polling trigger — poll GET /v1/items?updated_since={{lastPoll}}&per_page=50. Results are newest-updated first, so each poll returns only what changed since the previous run.
"Find item" search step — use GET /v1/items/{id} to look up a single item by its ID.

This integration pattern is available on the Studio tier.

A published Zapier app is on the roadmap. Until it ships, connect via the custom integration flow using your Personal Access Token.

In this section

Authentication

Rate limits

Responses & pagination

Endpoints

Item schema

Policy schema

Errors

Interactive reference

An interactive version of this reference — rendered from the OpenAPI 3.1 spec — is available at /api/v1/docs. The same adequacy disclaimers that appear in every API response are reproduced there in plain English, anchored at #adequacy-disclaimer. Every _meta.documentation_url in an API response links directly to that section.

The raw OpenAPI 3.1 spec is available at /api/v1/openapi.json. You can import it into Postman, Insomnia, or any OpenAPI-compatible tool.

What the API does not do

The v1 API is read-only. Creating, updating, or deleting data (POST/PUT/DELETE), webhooks, GraphQL, bulk export, and OAuth are not part of v1.

The coverage_state and gap_amount fields describe your inventory valuation status — whether an item's value is recorded and declared — not whether your insurance policy will actually pay out. They are not an adequacy assessment. See Item schema.

API