Allowed beacon domains API - PUT configuration

Updates the configuration of the allowed beacon origins for Cross Origin Resource Sharing (CORS) requests.

The request consumes an application/json payload.

PUT
  • Managed https://{your-domain}/e/{your-environment-id}/api/config/v1/allowedBeaconOriginsForCors
  • SaaS https://{your-environment-id}.live.dynatrace.com/api/config/v1/allowedBeaconOriginsForCors

Authentication

To execute this request, you need the Write configuration (WriteConfig) permission assigned to your API token. To learn how to obtain and use it, see Tokens and authentication.

Parameters

Parameter Type Description In Required
body AllowedBeaconOrigins

The JSON body of the request. Contains the configuration of the allowed beacon origins for CORS requests.

body optional

Body format

The AllowedBeaconOrigins object

Configuration of the allowed beacon origins for CORS requests.

Element Type Description Required
allowedBeaconOrigins BeaconDomainPattern[]

A list of allowed beacon origins for CORS requests.

optional
rejectBeaconsWithoutOriginHeader boolean

Discard (true) or keep (false) beacons without the Origin HTTP header on the BeaconForwarder.

If not set, false is used.

optional

The BeaconDomainPattern object

Allowed beacon origin for CORS requests.

Element Type Description Required
domainNameMatcher string

The matching operation for the domainNamePattern.

required
domainNamePattern string

The pattern of the allowed domain name.

required

Response

Response codes

Code Description
204

Success. The configuration has been updated. Response doesn't have a body.

400

Failed. The input is invalid.

Response body

A successful request doesn't return any content.

Validate payload

We recommend that you validate the payload before submitting it with an actual request. A response code of 204 indicates a valid payload.

The request consumes an application/json payload.

POST
  • Managed https://{your-domain}/e/{your-environment-id}/api/config/v1/allowedBeaconOriginsForCors/validator
  • SaaS https://{your-environment-id}.live.dynatrace.com/api/config/v1/allowedBeaconOriginsForCors/validator

Authentication

To execute this request, you need the Write configuration (WriteConfig) permission assigned to your API token. To learn how to obtain and use it, see Tokens and authentication.

Response

Response codes

Code Description
204

Success. The submitted configuration is valid. Response doesn't have a body.

400

Failed. The input is invalid.

Response body

A successful request doesn't return any content.