/redirect_flows* → endpoint removal
GoCardless API
Deprecated, no date
GoCardless has deprecated the /redirect_flows* endpoints without announcing a shutdown date. The provider considers these legacy APIs, and calls to them fail for new integrators. Existing integrations risk failure as the functionality is phased out.
Calls it hits
/redirect_flows*
What to use instead of these calls
Set up mandates using a Billing Request via POST /billing_requests along with a Billing Request Flow via POST /billing_request_flows instead of using /redirect_flows.
In GoCardless API's words
Redirect Flows are legacy APIs and cannot be used by new integrators. The Billing Request flow API should be used for your payment flows.
Facts
- API
- GoCardless API
api.gocardless.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against GoCardless API's own pages
Questions
When does this change take effect?
GoCardless API deprecated /redirect_flows* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: GoCardless 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 GoCardless API 1
-
No date
/payer_authorisations*Endpoint 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.