Tally API

The Tally API gives developers full programmatic control over forms and submissions. Create forms on the fly, sync responses to your stack, and automate workflows, all for free. Whether you're building a client portal, an internal tool, or an automated pipeline, the API makes it possible without a single click in the UI.

The Tally API is available for free to all Tally users.

API developer docs

Introduction - Tally Developer Docs

Fundamental concepts of Tally's API.

https://developers.tally.so/api-reference/introduction

Want to use Tally with your AI assistant? The Tally MCP server lets you build, update, and fetch forms using natural language, no API calls required. It's the fastest way to manage Tally through AI tools like Claude, Cursor, or Claude Code.

API reference basics

• Base URL: https://api.tally.so

• Authentication: every request needs an Authorization: Bearer <token> header. Get your API key here.

• Rate limits: 100 requests/minute. Use webhooks instead of polling to avoid hitting this.

• Versioning: the API is versioned by date. Pin a version with the tally-version header (e.g. tally-version: 2025-02-01) so future changes don't break your integration.

• Pagination: Pagination: list endpoints (GET /forms, GET /forms/{formId}/submissions) return paginated results — pass page and limit as request params, and check the hasMore boolean in the response (alongside page, limit, and total) before assuming you've got everything.

• Response codes:

Code	Meaning
200	Success - The request completed successfully
400	Bad Request - The request was malformed or contained invalid parameters
401	Unauthorized - Authentication credentials are missing or invalid
403	Forbidden - You don’t have permission to access this resource
404	Not Found - The requested resource doesn’t exist
429	Rate Limited - You’ve exceeded the allowed number of requests
500	Server Error - Something went wrong on our end

API use cases

• Programmatically create forms

• Duplicate and personalize a form for a new client; to do so fetch an existing form's structure, then create a new one from it:

curl --request POST \
  --url https://api.tally.so/forms \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "status": "PUBLISHED", "blocks": [ { "uuid": "<title-block-uuid>", "type": "FORM_TITLE", "payload": { "title": "Client Intake – Acme Co" } }, ...copied from GET /forms/{formId} ] }'

• Enable/disable fields based on business rules or time

• Dynamically change field visibility or values

• Auto-update dropdown options from live data sources (e.g. Notion, Airtable, Google Sheets); to do so pull the latest values from your source, then push them into the form's block schema:

# 1. Fetch the full form — you need every block, not just the dropdown
curl --request GET \
  --url https://api.tally.so/forms/{formId} \
  --header 'Authorization: Bearer <token>'

# 2. Each dropdown choice is its own DROPDOWN_OPTION block, sharing a
#    groupUuid with the DROPDOWN block. Update the ones you need:
#    { "uuid": "<option-uuid>", "type": "DROPDOWN_OPTION", "groupUuid": "<dropdown-group-uuid>", "payload": { "text": "Option A" } }

# 3. PATCH back the ENTIRE blocks array — PATCH replaces the whole set,
#    so any block you leave out gets deleted
curl --request PATCH \
  --url https://api.tally.so/forms/{formId} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "blocks": [ ...full blocks array from step 1, with the DROPDOWN_OPTION blocks updated... ] }'

• Filter and sync submissions into external tools (CRMs, dashboards, databases), to do so list new submissions and forward them downstream:

curl --request GET \
  --url https://api.tally.so/forms/{formId}/submissions \
  --header 'Authorization: Bearer <token>'

• Delete submissions programmatically

curl --request DELETE \
  --url https://api.tally.so/forms/{formId}/submissions/{submissionId} \
  --header 'Authorization: Bearer <token>'

API Frequently Asked Questions