POST /checkout/v{}/originKeys → endpoint removal
Adyen APIDeprecated, no date
The provider deprecated POST /checkout/v{}/originKeys without a shutdown date. This change affects calls to the POST /checkout/v{}/originKeys endpoint, which Adyen marked as deprecated in version 67. Once removed, requests to this operation fail.
Calls it hits
POST /checkout/v{}/originKeys
What to use instead of these calls
Authenticate Drop-in and Components with a client key instead of origin keys. You can generate the client key in the Customer Area or with the Management API.
In Adyen API's words
Deprecated in version 67 This operation takes the origin domains and returns a JSON object containing the corresponding origin keys for the domains.
Facts
- API
- Adyen API
*.adyenpayments.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Adyen API's own pages
Questions
When does this change take effect?
Adyen API deprecated POST /checkout/v{}/originKeys without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Adyen 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 Adyen API 1
-
No date
/pal/servlet/Payout/*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.