Create originKey values for domains

post/originKeys

This operation takes the origin domains and returns a JSON object containing the corresponding origin keys for the domains.

If you're still using origin key for your Web Drop-in or Components integration, we recommend switching to client key. This allows you to use a single key for all origins, add or remove origins without generating a new key, and detect the card type from the number entered in your payment form.

Endpoint destination URL
https://checkout-test.adyen.com/v41/originKeys
Idempotency-Keystring

A unique identifier for the message with a maximum of 64 characters (we recommend a UUID).

originDomainsarray[string]Required

The list of origin domains, for which origin keys are requested.

After submitting a call, you receive a response message to inform you that your request was received and processed.

Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.

HTTP Responses

  • 200 - OK

    The request has succeeded.

  • 400 - Bad Request

    A problem reading or understanding the request.

  • 401 - Unauthorized

    Authentication required.

  • 403 - Forbidden

    Insufficient permissions to process the request.

  • 422 - Unprocessable Entity

    A request validation error.

  • 500 - Internal Server Error

    The server could not process the request.