Stripe API
collect body parameter removal on POST /v1/account_links
Deprecated, no dateSubscribe to Stripe APIShare
Stripe API deprecated POST /v1/account_links, body parameter collect without giving a shutdown date yet.
Calls it hits
POST /v1/account_linksbody parameter collect
What to use instead of these calls
Send collection_options (fields, future_requirements) instead of collect.
In Stripe API's words
The collect parameter is deprecated. Use `collection_options` instead.
Facts
- API
- Stripe API
api.stripe.com - Kind
- Parameter removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Stripe API's own pages
Questions
When does this change take effect?
Stripe API deprecated POST /v1/account_links, body parameter collect without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Stripe API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Stripe API 7
-
No date
POST /v1/chargesEndpoint removal Deprecated, no date -
No date
POST /v1/charges/{id}/captureEndpoint removal Deprecated, no date -
No date
POST /v1/issuing/authorizations/{id}/approveEndpoint removal Deprecated, no date -
No date
POST /v1/issuing/authorizations/{id}/declineEndpoint removal Deprecated, no date -
No date
/v1/customers/{id}/cards*Removal Deprecated, no date -
No date
/v1/sources*Removal Deprecated, no date -
No date
POST /v1/accountsParameter removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.