tally.

create a key on tally.so/settings/api-keys (Settings → API keys → Create API key), then paste it into oto. It is only shown once.

six tools, verb in op:

four operations destroy something; all accept dry_run=True, which validates identically and returns a real diff instead of writing:

this is the costliest trap of this API, recorded live:

the connector therefore translates no 401 into "key rejected" — even without known context, the message names both causes and points to tally_account(op="me"), which settles it: if it answers, the key is good and it is the plan that blocks.

derived from the real OpenAPI 3.0.1 spec (developers.tally.so/api-reference/openapi.json, read on 2026-08-31), and tested live on 2026-08-31 with a real tly- key on a FREE account.

exercised for real, conforms to the code: op="me"; the full cycle of a form (create → read → rename → publish → trash); questions; responses (list + filter=partial); the five analytics views; the full cycle of a webhook (create → list → event log → merged PATCH → delete) — including the check that op="update" with only is_enabled=False does not wipe the URL; the refusal of an irrelevant argument; and the fact that dry_run writes nothing and never echoes the signing_secret. The account was returned to its initial state (0 forms, 0 webhooks).

envelopes recorded (the spec did not settle them): /forms and /workspaces return {items, page, limit, total, hasMore}; /webhooks returns {webhooks, …} and not items; /forms/{id}/questions returns {questions, hasResponses}; /organizations/{id}/users and .../invites return a bare array; webhook PATCH/DELETE return an empty body.

NOT exercised, for lack of plan or material, and therefore derived from the spec alone: reading/writing blocks (plan 401), writing workspaces and anything touching folders (Pro), update_question (a freshly created form returns no question, even published), reading and deleting ONE response (no response on the account), invitations (would send real emails), removing a member (would remove the owner from their own org and revoke the call's key), replaying an event (no event delivered).

a question takes its title from the `LABEL` block that precedes it: a form whose inputs have no LABEL returns {"questions": [], "hasResponses": false} even published — it is not a bug, there is simply nothing to name. Found live after believing an endpoint was broken.

⚠️ `metrics` and `drop_off` do not give the same `completionRate` over the same period (100 vs 50 on one visit and one submission, measured): they do not count the same thing. Do not mix them in one dashboard without saying which one is cited.

block traps met at creation: a TITLE or LABEL block must not share its groupUuid with an input block, and TitlePayload carries html, not title (only FormTitlePayload has both).

this connector accepts multiple comptes: each stored credential becomes a named account (one name per compte), at your level, your team's or your org's.