Repository navigation
feat(item): add fetchItemsCursor and fetchAllItems for GET /v2/items - #185
Merged
Merged
Conversation
This was referenced Oct 5, 2026
Merged
FranDisalvo90
approved these changes
Oct 5, 2026
cernadasjuan
approved these changes
Oct 5, 2026
Gabrielpanga
force-pushed
the
fix/encode-query-values
branch
from
October 5, 2026 13:11
8705d5f to
66f5a90
Compare
Gabrielpanga
force-pushed
the
feat/list-items-cursor
branch
from
October 5, 2026 13:11
89ab7b2 to
beab0d5
Compare
Opt-in, paid plans only: teams without the feature enabled get 403 LIST_ITEMS_FEATURE_NOT_ENABLED.
Gabrielpanga
force-pushed
the
feat/list-items-cursor
branch
from
October 5, 2026 13:20
beab0d5 to
84be18a
Compare
pluggy-github-app Bot
pushed a commit
that referenced
this pull request
Oct 8, 2026
# [0.92.0](v0.91.0...v0.92.0) (2026-10-08) ### Bug Fixes * **api:** URL-encode query string values ([#184](#184)) ([16f0596](16f0596)) * **deps:** patch handlebars, http-cache-semantics and brace-expansion advisories ([#187](#187)) ([0ef8d00](0ef8d00)) ### Features * add Smart Transfer linkedJourney, data consent and source account balance ([#186](#186)) ([c77e1c3](c77e1c3)) * **item:** add fetchItemsCursor and fetchAllItems for GET /v2/items ([#185](#185)) ([7a82811](7a82811)) * sync with the API spec (card metadata, SCR, merchants, category rules, pix-qr, boletos) ([#183](#183)) ([d0f0c86](d0f0c86))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
Opt-in, paid plans only. Listing items is disabled by default and is only available to paid-plan teams that have explicitly requested it from Pluggy support. Teams without it enabled get
403 LIST_ITEMS_FEATURE_NOT_ENABLED. This is stated at the top of the JSDoc of every new method and type, and in the README.Note
Stack: #183 → #184 → this PR. Merge in that order; GitHub retargets each one as the previous lands. Without #184 a cursor containing
+would reach the API corrupted.What
fetchItemsCursor(options?: ItemCursorFilters): one page ofGET /v2/items, newest first.fetchAllItems(options?): followsnextacross every page, same loop asfetchAllTransactions.ItemCursorFilters:clientUserId,connectorId,after. Only those three are sent, even if a caller passes extra fields at runtime, because the API rejects unknown query params.For most integrations the recommended path is still to store each
itemIdwhen it is created (Pluggy ConnectonSuccessor theitem/createdwebhook) and callfetchItem(id).Tests
tests/itemsCursor.test.ts(9, nock): no params on the first page, filters as query params, a cursor with+ / =sent intact, extra fields dropped, a 3-page sweep forwarding filters, stop whennexthas noafter, and the 403 body reaching the caller from both methods.pnpm test: 71/71.