Create originKey values for domains
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.
A unique identifier for the message with a maximum of 64 characters (we recommend a UUID).
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.
200 - OK
The request has succeeded.Show more
400 - Bad Request
A problem reading or understanding the request.Show more
401 - Unauthorized
Authentication required.Show more
403 - Forbidden
Insufficient permissions to process the request.Show more
422 - Unprocessable Entity
A request validation error.Show more
500 - Internal Server Error
The server could not process the request.Show more