Create originKey values for one or more merchant domains in Adyen Checkout Utility
A documented Adyen Checkout Utility operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Create originKey values for one or more merchant domains.
- POSTChanges data
checkout-test.adyen.com/originKeys
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Adyen Checkout Utility operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Questions
- Can HumDay create originkey values for one or more merchant domains in Adyen Checkout Utility?
- Yes. This operation is published in Adyen Checkout Utility's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Adyen Checkout Utility data?
- Yes — this is a POST operation, so it changes something in Adyen Checkout Utility. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Adyen Checkout Utility account.
Where this came from
Read from a published API description for Adyen Checkout Utility at raw.githubusercontent.com/adyen/adyen-openapi/master/specs/3.0/CheckoutUtilityService-v1.j. The description above is the provider’s own wording, not ours. Last published 2021-06-18.