Overview
The Recurring Transactions API (also called Recurrences) allows you to set up automatic transaction creation based on flexible schedules. Perfect for salary, rent, subscriptions, and any regularly occurring financial activity.List All Recurring Transactions
GET /v1/recurrences
Query Parameters
Page number for pagination
Response Fields
Recurrence ID
ISO 8601 timestamp of creation
ISO 8601 timestamp of last update
Transaction type:
withdrawal, deposit, or transferRecurrence title
Recurrence description
First occurrence date (ISO 8601)
Date of last created transaction (ISO 8601)
End date for recurrence (ISO 8601)
Whether to apply rules to created transactions
Whether the recurrence is active
Number of times to repeat (null for unlimited)
Recurrence notes
Array of repetition schedules
Array of transaction templates
Create Recurring Transaction
POST /v1/recurrences
Request Body
Transaction type:
withdrawal, deposit, or transferRecurrence title (1-255 characters, must be unique)
Recurrence description (1-32,768 characters)
First occurrence date (YYYY-MM-DD)
End date (YYYY-MM-DD)
Number of repetitions (1-31, conflicts with repeat_until)
Apply transaction rules to created transactions
Whether the recurrence is active
Recurrence notes
Array of repetition objects (minimum 1)
Array of transaction templates (minimum 1)
Repetition Object Fields
Repetition type:
daily, weekly, ndom, monthly, yearlyWhen to trigger (0-10, meaning depends on type)
Periods to skip (0-31)
Weekend handling: 1=skip to Monday, 2=skip to Friday, 3=skip to next Friday, 4=no adjustment
Transaction Template Fields
Transaction description (1-255 characters)
Transaction amount (positive number)
Foreign currency amount
Currency ID
Currency code (3-51 characters)
Foreign currency ID
Foreign currency code
Source account ID (must belong to user)
Source account name (1-255 characters)
Destination account ID
Destination account name
Budget ID (must belong to user)
Budget name (1-255 characters)
Category ID (must belong to user)
Category name (1-255 characters)
Piggy bank ID (must belong to user)
Piggy bank name (1-255 characters)
Comma-separated tags (1-255 characters)
Repetition Types:
- daily: Every day (moment not used)
- weekly: Every week on day X (moment: 1=Monday, 7=Sunday)
- monthly: Every month on day X (moment: 1-31)
- ndom: Nth day of month (moment: “1.1” = first Monday)
- yearly: Every year on date from first_date (moment not used)
Weekend Handling:
- Skip to Monday: If falls on weekend, move to next Monday
- Skip to Friday: If falls on weekend, move to previous Friday
- Skip to next Friday: If falls on weekend, move to next Friday
- No adjustment: Create transaction on the scheduled date regardless
Get Recurring Transaction by ID
GET /v1/recurrences/{id}
Returns the same response fields as the List endpoint.
Update Recurring Transaction
PUT /v1/recurrences/{id}
Accepts the same parameters as Create Recurring Transaction. All fields are optional.
Delete Recurring Transaction
DELETE /v1/recurrences/{id}
Deletes the recurring transaction. Previously created transactions remain.
Trigger Recurring Transaction
POST /v1/recurrences/{id}/trigger
Manually triggers the recurrence to create the next transaction immediately.
Related Endpoints
Get Recurring Transaction’s Created Transactions
GET /v1/recurrences/{id}/transactions
Returns all transactions that were created by this recurrence.
Query Parameters
Page number for pagination
Start date filter (YYYY-MM-DD)
End date filter (YYYY-MM-DD)
Best Practices
Choosing End Conditions
You can end a recurrence in three ways:- No end date: Leave both
repeat_untilandnr_of_repetitionsnull for unlimited recurrence - End by date: Set
repeat_untilto a specific date - End by count: Set
nr_of_repetitionsto limit occurrences
Common Recurring Patterns
Monthly Bills:Maintenance Tips
- Review regularly: Check recurrences quarterly to ensure they’re still accurate
- Update amounts: Adjust when bills change (rent increases, subscription price changes)
- Set active=false: Instead of deleting, deactivate recurrences you might need later
- Use descriptive titles: Include frequency and amount for easy identification