/payer_authorisations* → endpoint removal
GoCardless API
Deprecated, no date
GoCardless has deprecated the /payer_authorisations* endpoints without a shutdown date. The provider notes that it is a legacy API that cannot be used by new integrators. Calls to these endpoints fail for integrations that do not already have access.
Calls it hits
/payer_authorisations*
What to use instead of these calls
Collect the payer's details and create mandates using the Billing Request API instead. Use POST /billing_requests and its related actions rather than /payer_authorisations.
In GoCardless API's words
Payer Authorisation is legacy API and cannot be used by new integrators. The Billing Request API should be used for any new integrations.
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 /payer_authorisations* 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
/redirect_flows*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.