Connect RowFold to Zapier — 4 · Read and write anything: the REST API

When a Zap needs to look something up, update an existing record, or work across tables, use the API directly. 1. In Developers → API clients, create a client with the scopes you need. The secret is shown once. 2. Exchange it for a token: POST /api/v1/auth/token with {"clientId": "rfc_…", "clientSecret": "rfsk_…"}. Note the response is camelCase, not the RFC 6749 spelling: accessToken, tokenType, expiresIn, scope. 3. Call the API from Webhooks by Zapier → Custom Request with the header Authorization: Bearer . The access token lasts one hour, which is the honest catch with this route inside Zapier: a step holding a pasted token will start failing the same day. For a Zap, prefer the webhook recipes (1–3) and keep the API for a step that fetches its own token first, or for your own code. The full reference is at /Developers/Docs, and the OpenAPI document at /api/v1/openapi.json feeds Postman and code generators without credentials.