Get a key
- In the Money Tracker app, open Profile and choose API keys.
- Tap Create key, give it a name and tick what it may do.
- Copy the API_KEY and the API_SECRET. The secret is shown only once.
Each account can have one active key. To replace it, revoke it on the same screen and create a new one. A revoked key stops working right away.
Authentication
Send both values as headers on every request. Never put the secret in a URL, a web page or an app that other people can open.
- X-Api-Key
- Your API_KEY. It starts with mtu_.
- X-Api-Secret
- Your API_SECRET, 40 letters and digits.
curl "https://moneytracker.arizu.id/api/v1/transactions?month=2026-11&type=income" \
-H "X-Api-Key: mtu_YOUR_API_KEY" \
-H "X-Api-Secret: YOUR_API_SECRET"Permissions
A key gets only the permissions you tick. A write permission includes read.
- transactions:read
- Read transactions
- transactions:write
- Record, change and delete transactions
- categories:read
- Read categories
- categories:write
- Add and delete categories
- money_sources:read
- Read money sources and their balances
- money_sources:write
- Add, change and delete money sources
- profile:read
- Read the account name, email, currency, language and plan
Endpoints
Paths are relative to the base URL. Amounts are in the account currency.
Account
-
GET
/api/v1/auth/meprofile:readThe account profile.
Transactions
-
GET
/api/v1/transactionstransactions:readTransactions, newest first. Filters: month (2026-11), type (income or expense), source_id, page, per_page (up to 100).
-
GET
/api/v1/transactions/{id}transactions:readOne transaction.
-
POST
/api/v1/transactionstransactions:writeRecord a transaction. Required: type, amount, occurred_on (2026-11-02). Optional: category_id, payment_source_id, note (up to 255 characters), client_ref.
-
PUT
/api/v1/transactions/{id}transactions:writeChange a transaction. Send the same fields as when you record one, without client_ref.
-
DELETE
/api/v1/transactions/{id}transactions:writeDelete a transaction.
Categories
-
GET
/api/v1/categoriescategories:readIncome and expense categories.
-
POST
/api/v1/categoriescategories:writeAdd a category. Required: type, name. Optional: icon, color (#RRGGBB), client_ref.
-
DELETE
/api/v1/categories/{id}categories:writeDelete a category.
Money sources
-
GET
/api/v1/payment-sourcesmoney_sources:readMoney sources with their balances.
-
POST
/api/v1/payment-sourcesmoney_sources:writeAdd a money source. Required: type (bank, card, ewallet or cash), holder_name. Optional: bank_name, provider_name, card_type, card_last4, opening_balance, client_ref.
-
PUT
/api/v1/payment-sources/{id}money_sources:writeChange a money source.
-
DELETE
/api/v1/payment-sources/{id}money_sources:writeDelete a money source.
Every other path answers 403 to an API key, even when the app itself uses it.
Example: record a sale
A point of sale can record each sale as income. Give every sale its own client_ref, so a retry after a network error does not record the sale twice.
curl -X POST "https://moneytracker.arizu.id/api/v1/transactions" \
-H "X-Api-Key: mtu_YOUR_API_KEY" \
-H "X-Api-Secret: YOUR_API_SECRET" \
-H "Content-Type: application/json" \
-d '{
"type": "income",
"amount": 125000,
"occurred_on": "2026-11-02",
"note": "Sale 1042",
"client_ref": "pos-sale-1042"
}'The reply has status 201 and the new transaction id in data.id.
{
"data": {
"id": 58213,
"amount": "125000.00",
"currency": "IDR",
"original_amount": null,
"original_currency": null,
"fx_rate": null,
"fx_date": null
}
}client_ref is 8 to 64 letters, digits or dashes. When the account already has a transaction with the same client_ref, the API returns that transaction instead of recording a new one.
Responses and errors
A successful reply puts the result in data. A failed reply has a message in error, in the language of the account, and often a code that is the same in every language.
{
"error": "This API key does not have the permission for this request",
"code": "api_key_scope_missing",
"scope": "transactions:write"
}- 401
- The key or secret is missing or wrong, or the key was revoked or has expired.
- 403
- The key does not have the permission for this request, the path is closed to API keys, or the account is blocked.
- 404
- The item does not exist in this account.
- 422
- A field is missing or not valid. When fields is present, it lists what to fix.
- 429
- Too many requests. Wait the number of seconds in the Retry-After header.
Limits
Each key can make up to 60 requests a minute. Your plan limits still apply, the same as in the app. On the Free plan that means up to 30 new transactions a day.
Keep your keys safe
- Keep the secret in one place, such as the settings of your point of sale, and do not share it in chats or email.
- Tick only the permissions the system needs.
- If a secret leaks, revoke the key in the app and create a new one.
- The app shows when your key was last used. If that does not match your own systems, revoke the key.
Questions about the API? Write to ariefzufar@arizu.id / arizu.team@gmail.com.