Get an allowed origin
Returns the allowed origin identified in the path.
To make this request, your API credential must have the following roles:
- Management API—API credentials read and write
In: header
Path Parameters
The unique identifier of the merchant account.
Unique identifier of the API credential.
Unique identifier of the allowed origin.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/merchants/string/apiCredentials/string/allowedOrigins/string"Example response for getting an allowed origin for the API credential.
{ "id": "YOUR_ALLOWED_ORIGIN", "domain": "https://www.eu.mystore.com", "_links": { "self": { "href": "https://management-test.adyen.com/v1/merchants/YOUR_MERCHANT_ACCOUNT/apiCredentials/YOUR_API_CREDENTIAL/allowedOrigins/YOUR_ALLOWED_ORIGIN" } }}Create an allowed origin POST
Adds a new [allowed origin](https://docs.adyen.com/development-resources/client-side-authentication#allowed-origins) to the API credential's list of allowed origins. To make this request, your API credential must have the following [roles](https://docs.adyen.com/development-resources/api-credentials#api-permissions): * Management API—API credentials read and write
Delete an allowed origin DELETE
Removes the [allowed origin](https://docs.adyen.com/development-resources/client-side-authentication#allowed-origins) identified in the path. As soon as an allowed origin is removed, we no longer accept client-side requests from that domain. To make this request, your API credential must have the following [roles](https://docs.adyen.com/development-resources/api-credentials#api-permissions): * Management API—API credentials read and write
