-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nested retrieve doesn't accept stripe_account
#609
Comments
Hi @ryancausey, thanks for the report. Indeed, it looks like the We'll work on a fix, but note that we no longer recommend using instance methods on list objects. Instead, you can retrieve nested resources by using the static methods on the parent resource, e.g. to retrieve a card: source = stripe.Customer.retrieve_source('cus_123', 'card_123', stripe_account='acct_123') |
Thanks for the response @ob-stripe. Are these methods being deprecated? |
We might remove them in a future (major) version of the library, but haven't made firm plans yet. We recommend using the static methods because they avoid making unnecessary requests (e.g. you don't need to retrieve the customer object first to access a card on the customer if you already have the customer ID and the card ID in your database). |
Just released stripe-python 2.36.0. The |
During testing the python API, it appears that making a nested retrieve call doesn't accept the
stripe_account
as a parameter. Is this expected behavior? Does the nested retrieve use the parent stripe object'sstripe_account
it was retrieved with?In this case I was retrieving sources for a customer. To reproduce:
customer
object usingstripe_account=<account id>
.customer.sources
passingstripe_account=<account id>
The text was updated successfully, but these errors were encountered: