GET /transactions ignores limit and offset query parameters

[pr1001]

Description

The GET /v1/transactions endpoint documentation states that limit and offset query parameters are supported:

• limit: "Sets the maximum number of records to return." Defaults to 1,000.
• offset: "Sets the offset for the records returned"

However, these parameters are completely ignored by the API.

Steps to Reproduce

1. Make a request to GET /v1/transactions with a date range that returns multiple transactions
2. Note the count of transactions returned
3. Make the same request with limit=5
4. Observe that the same number of transactions is returned (not 5)
5. Make a request with limit=3&offset=3
6. Observe the same transactions are returned, with the same first transaction ID

Test Results

# Test 1: Default (no limit/offset)
# Count: 47 transactions

# Test 2: With limit=5
# Count: 47 transactions (expected: 5)

# Test 3: With limit=3 offset=3
# Count: 47 transactions (expected: 3)
# First transaction ID is identical to Test 1 (offset not applied)

Expected Behavior

• limit=5 should return only 5 transactions
• offset=3 should skip the first 3 transactions
• has_more should return true when there are more transactions beyond the limit

Actual Behavior

• limit and offset parameters are ignored
• All transactions within the date range are returned regardless of these parameters
• has_more always returns false

Impact

This prevents:

• Efficient pagination for large transaction sets
• Reducing API response payload sizes
• Building proper pagination UI in third-party apps

Workaround

Currently the only way to limit results is to use narrower date ranges (e.g., 3-7 days instead of months).

Environment

• API Endpoint: https://dev.lunchmoney.app/v1/transactions
• Date tested: 2026-01-10

---

This issue was created with assistance from Claude Code.

[jpjpjp]

Hi @pr1001 thanks for reporting this.

We had a regression in the v1/transactions API that broke the behavior of the limit and offset parameters. This has been fixed and should be working as described in the docs.