feat(api): add pagination support to /cash/agents endpoint - #115
Closed
dominiccreates wants to merge 2 commits into
Closed
feat(api): add pagination support to /cash/agents endpoint#115dominiccreates wants to merge 2 commits into
dominiccreates wants to merge 2 commits into
Conversation
|
@dominiccreates is attempting to deploy a commit to the jotelfootball-tech's projects Team on Vercel. A member of the Team first needs to authorize it. |
dominiccreates
force-pushed
the
feat/agents-pagination
branch
from
July 17, 2026 12:30
7566ae3 to
52fda4c
Compare
Contributor
|
Fix conflict |
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
2 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.
Closes #91 This pull request proactively adds pagination support to endpoints returning growing lists (starting with the /api/v1/cash/agents endpoint as a reference implementation) to prevent unbounded list retrieval at scale.
We have adopted a consistent offset-based pagination pattern.