---
title: "Create originKey values for domains"
method: POST
path: "/originKeys"
tags: ["Utility"]
deprecated: true
---

# Create originKey values for domains

`POST /originKeys`

> **Deprecated.**

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](https://docs.adyen.com/development-resources/client-side-authentication/migrate-from-origin-key-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.

## Headers

- `Idempotency-Key` string

## Request body

- UtilityRequest
  - `originDomains` string[], required — The list of origin domains, for which origin keys are requested.

## Response `200`

OK - the request has succeeded.

- UtilityResponse
  - `originKeys` object — The list of origin keys for all requested domains. For each list item, the key is the domain and the value is the origin key.

## Other responses

- `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.

---

[API](https://skmtc.net/adyen/apis/checkoutservice.md) · [All operations](https://skmtc.net/adyen/apis/checkoutservice/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/adyen/checkoutservice/revisions/a2d1f411288c/schema)