-
Notifications
You must be signed in to change notification settings - Fork 547
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
Expose connect account id in Stripe::StripeObject #1101
Comments
@ryanseys I'm not sure I follow the feature request here. To retrieve an object in the API you already have to know which account you're making the request on, either based on the API key you use or by setting the right account id |
I agree with the sentiment, however when we're passing around these If it was easier for us to access the stripe connect account id in this object, we wouldn't need to pass around a reference to it whenever we want to pass this Stripe::StripeObject around. I'm not saying we don't already know it, I'm just saying if it was more cleanly exposed via this SDK, it could greatly simplify some of our code and give us more confidence that we're always using the correct connect account id. |
That's fair but the SDK is mostly exposing what is in the API and we don't expose an I'll keep it as a feature request to see if other developers would like to see a similar change though |
Sounds good! I understand if it's not feasible. |
Is your feature request related to a problem? Please describe.
I'd like to get access to the Stripe connect account id e.g.
acct_123
associated with aStripe::StripeObject
.Currently the only way to do this through publicly accessible methods is via
Stripe::StripeObject#marshal_dump
like so:This is pretty clunky.
Describe the solution you'd like
Exposing a method like so would be nice:
Or even an object that wraps all those client values that we can more easily dig into:
Could also expose
api_version
via a similar mechanism.Describe alternatives you've considered
Seems like this is the only way to do this right now:
Additional context
No response
The text was updated successfully, but these errors were encountered: