Adyen API (checkout-test.adyen.com)
POST /v{id}/originKeys endpoint removal
Deprecated, no dateSubscribe to Adyen API (checkout-test.adyen.com)Share
Adyen has deprecated POST /v{id}/originKeys without a shutdown date. The endpoint, which generates origin keys for origin domains, fails when called. It was deprecated in version 67.
Calls it hits
POST /v{id}/originKeys
What to use instead of these calls
Authenticate Drop-in and Components with a client key instead of origin keys. You can generate a client key in the Customer Area or with the Management API.
In Adyen API (checkout-test.adyen.com)'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 (checkout-test.adyen.com)
checkout-test.adyen.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Adyen API (checkout-test.adyen.com)'s own pages
Questions
When does this change take effect?
Adyen API (checkout-test.adyen.com) deprecated POST /v{id}/originKeys without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Adyen API (checkout-test.adyen.com) 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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.