feat(wallets): Move wallets API under customers#366
Open
Conversation
This was referenced Feb 12, 2026
vincent-pochet
approved these changes
Feb 12, 2026
6196069 to
f834aad
Compare
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
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.
Context
The PR implements api for
/customers/:customer_external_id/walletsand/customers/:customer_external_id/wallets/:code/metadataendpoints.Related PR: getlago/lago-api#4995
Description
The new customer wallets and metadata API looks like this 👇
And for the metadata:
Nested Commands
Similar to Ruby, this PR introduces a few new nested mixins that add support for nested resources. They're pretty close to the single-resource mixins, with a couple of differences:
updatetakes the resource ids first, and then the params as the last argument,timeoutoption for all methods, andoptionsforfind_all, have to be passed as keyword arguments only