Choose the smallest complete set of permissions your application needs. This page is generated from the published @lunch-money/v2-api-spec/oauth-scopes catalog; do not edit it by hand.
Scopes are fixed when you create a client
Authorization requests omit scope. To change permissions later, create and review a replacement client, update your integration, and ask every user to authorize it.
Scope groups
Groups are selection shortcuts, not extra permissions. Every predefined group includes me:read so an application can identify the authorized Lunch Money user and budget account. A group expands to the exact scopes listed below.
Read only
View all supported Lunch Money data without changing it
View transaction attachment metadata and get download access to attachments
getTransactionAttachmentUrl
transaction_attachments:create
Attach files to transactions
attachFileToTransaction
transaction_attachments:delete
Delete transaction attachments
deleteTransactionAttachment
tags:read
View tags
getAllTags, getTagById
tags:create
Create tags
createTag
tags:update
Update tags
updateTag
tags:delete
Delete tags
deleteTag
recurring_items:read
View recurring items
getAllRecurring, getRecurringById
budgets:read
View budget period settings
getBudgetSettings
budgets:update
Create or update budget amounts
upsertBudget
budgets:delete
Delete budget amounts
deleteBudget
Continued access
offline_access
Allow this app to maintain access without asking you to sign in and authorize it again
offline_access is not permission to a V2 resource. It allows an eligible token response to include a longer-lived, finite refresh token. Your application must still request every resource scope it needs when the client is created.
Find the scope for an endpoint
The V2 API reference displays the required OAuth scope for each operation. Scope requirements come from the same catalog and standard OpenAPI security metadata used to generate this page.