Start for free

API and MCP for your own tools

In Tetri, you can connect a script, a spreadsheet or an MCP client to the wallets, transactions, budgets and reports of your workspace. Each key has only the permissions you pick and lasts 90 days at most.

Compare plansCreate a key

The response to POST /transactions/parse with a phrase like "coffee 3 euros yesterday": a draft with the amount, currency, date, wallet and category, and a list of the missing fields. The request creates no transaction.

A separate key for each integration

In the "Create key" window you set a name, a client (REST API or MCP), a lifetime of 1 to 90 days and capabilities. Read is on from the start; you switch on creating transactions, templates and imports by hand.

You see the token once

You can copy the token from the create window. Later, the list shows only the prefix, and you cannot see the token again. Changing the password or the email address revokes all tokens.

REST: read, write and import

Base path /api/v1/programmatic. Creating needs an Idempotency-Key header of 16 to 128 characters. A repeated request creates no duplicate. The same value with a different body gets a 409 response.

MCP: only the allowed tools

The address is POST /mcp, the transport is Streamable HTTP without sessions, and the token goes in the Authorization: Bearer header. Only the tools the key allows are visible. There is one tool for writing: create_transaction.

Request log and usage

The log shows the time, key, action, transport, status and duration of each request. Usage is available for 7, 30 or 90 days. Request bodies are not stored.

Key permissions and restrictions

  • Key capabilities

    Read: wallets, transactions, budgets, recurring transactions, goals, insights, reports and import status. Write: transactions, templates, import upload and confirmation.

  • Keys

    Up to 5 active keys per user in one workspace. Lifetime from 1 to 90 days, 30 by default.

  • Limits per minute

    1,200 requests for reading, 120 for reports, insights, text parsing, and creating transactions and templates, and 5 for import upload and confirmation. Requests over the limit get a 429 response.

  • Import

    POST /imports: a file up to 10 MB in CSV, Excel, OFX, QFX or MT940 format and a wallet ID. After the check, confirm the import with a second request; the import skips duplicates.

  • Request check

    Each request passes two checks: the capabilities of the key and the permissions of the user in the workspace.

  • Key and workspace

    A key belongs to a user and to the workspace you created it in. It has no access to other workspaces.

Questions about API and MCP

Related sections

Connect your own tool

Create a key with read permissions and send the first request.

Plans and pricesStart for free