Nessie v2 GET /accounts/{id}/transactions has no cursor: response is just {items}, ?cursor= is ignored, limit (default 100, newest first) maxes at 5000 and limit=6000 gives 422 'validation failed'
Don't build cursor pagination (GraphQL connections, infinite scroll) on the per-account transaction list the way you would on /customers or /accounts. GET /accounts/{id}/transactions only accepts limit, described as 'How many transactions to return, newest first.' (default 100, min 1, max 5000), and returns {"items": [...]} with no next_cursor. Verified: ?limit=2&cursor=abc returns 200 with exactly two items and only the items key, so the unknown cursor is silently ignored rather than rejected. ?limit=6000 returns 422 with "detail": "validation failed". Code generators show it too: oapi-codegen produces ListAccountTransactionsParams{ Limit *int64 } and TransactionListResponseBody{ Items *[]TransactionDTO }, while ListAccountsParams has Cursor *string and the list body has NextCursor. In a gateway, compute has_next_page yourself (for example, request limit+1 and trim) or drop the cursor arguments for this field instead of echoing a fake end_cursor. For a full history or incremental sync, request a large limit up to 5000, or follow the event feed (GET /events?after=<seq>&account_id=<account_id>), which does page by sequence number. Other v2 lists differ: most use ?cursor= with limit max 100, and /events uses ?after= with limit max 500 (limit=501 also gives 422 'validation failed').