Skip to content
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

v4.0.0 idempotency_key parameter unknown #849

Closed
newenegue opened this issue Aug 2, 2022 · 3 comments · Fixed by #850
Closed

v4.0.0 idempotency_key parameter unknown #849

newenegue opened this issue Aug 2, 2022 · 3 comments · Fixed by #850
Assignees
Labels

Comments

@newenegue
Copy link

newenegue commented Aug 2, 2022

Describe the bug

Any of our requests to POST /v1/subscriptions, POST /v1/invoices and POST /v1/customers/:id are failing with Received unknown parameter: idempotency_key

To Reproduce

Make a request to create a customer and include the idempotency_key parameter

stripe.Customer.create(
  name="John Doe",
  email=email,
  idempotency_key="test-key-12345",
)

Expected behavior

idempotency_key is an accepted parameter

Code snippets

No response

OS

macOS

Language version

Python 3.7.3

Library version

stripe-python v4.0.0

API version

2019-05-16

Additional context

No response

@newenegue newenegue added the bug label Aug 2, 2022
@newenegue newenegue changed the title v.4.0.0 idempotency_key parameter unknown v4.0.0 idempotency_key parameter unknown Aug 2, 2022
@remi-stripe remi-stripe self-assigned this Aug 2, 2022
@remi-stripe
Copy link
Contributor

@newenegue thanks a lot for the report. There is definitely something wrong where some API methods don't handle options like idempotency_key and api_key properly but others do. We're investigating but for now you should roll back to the previous major.

@newenegue
Copy link
Author

@remi-stripe thanks for the response! We've rolled back to v3.5.0 and everything is working as expected.

@ramya-stripe
Copy link
Contributor

We have just released version 4.0.1 of the package which has the fix for this issue. Rolling back to previous major is no longer necessary.

@kamil-stripe kamil-stripe unpinned this issue Sep 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants