Introduction
Tally offers two ways to build integrations: a REST API for direct HTTP access and an MCP server for connecting AI agents. Both let you read and manage budgets, categories, transactions, and API keys. They share the same authentication and permission model.
All URLs below are relative to your site origin with the /api prefix (e.g. https://your-domain.com/api/v1/...).
Current version is v1 — all paths in this documentation use the /v1 prefix under /api.
What you can do
| Area | Capabilities |
|---|---|
| User | Read the signed-in user profile and subscription summary. |
| Budgets | List, create, update, and delete budgets; manage categories within a budget. |
| Transactions | List (with filters), create, update, and delete transactions. |
| Platform | Consistent errors, optional rate limiting, and cursor-based pagination on list endpoints. |
How this documentation is organized
- API keys & authentication — obtain a key from the developer portal and send
Authorization: Bearer. - Endpoints — request/response JSON examples for each route (except API-key management JSON, which stays in the portal).
- MCP connection — connect AI agents (Claude, Cursor, etc.) to your Tally data.
- Errors & rate limits — error body shape, common
typevalues, and throttling.
Machine-readable spec
Import OpenAPI 3.1 into Postman, Insomnia, or codegen tools. The spec matches the same routes described here.
Next step
Continue to API keys & authentication to create a key and make your first request.