• Home
  • Dynatrace API
  • Configuration
  • RUM
  • Content resources
  • PUT configuration

Content resources API - PUT configuration

Updates the configuration of content providers in your Dynatrace environment.

The request consumes an application/json payload.

PUTManaged https://{your-domain}/e/{your-environment-id}/api/config/v1/contentResources
SaaS https://{your-environment-id}.live.dynatrace.com/api/config/v1/contentResources
Environment ActiveGate https://{your-activegate-domain}/e/{your-environment-id}/api/config/v1/contentResources

Authentication

To execute this request, you need an access token with Write configuration (WriteConfig) scope. To learn how to obtain and use it, see Tokens and authentication.

Parameters

ParameterTypeDescriptionInRequired
bodyContentResources

The JSON body of the request. Contains the configuration of content resources.

bodyoptional

Request body objects

The ContentResources object

The configuration of content resources.

ElementTypeDescription
resourceProvidersResourceProvider[]

An ordered list of manually added content providers.

Rules are evaluated from top to bottom; the first matching rules applies.

Can be null.

resourceUrlCleanupRulesResourceUrlCleanupRule[]

An ordered list of resource URL cleanup rules.

Rules are evaluated from top to bottom; the first matching rules applies.

Can be null.

resourceTypesResourceType[]

An ordered list of manually defined resource types.

Rules are evaluated from top to bottom; the first matching rules applies.

Can be null.

The ResourceProvider object

A rule for the content provider.

ElementTypeDescription
resourceNamestring

The name of the provider.

resourceTypestring

The type of the provider.

The element can hold these values
  • CDN_RESOURCES
  • FIRST_PARTY_RESOURCES
  • THIRD_PARTY_RESOURCES
brandIconUrlstring

The URL of the provider's icon.

Can be null.

domainNamePatternsstring[]

A list of domain patterns of the provider.

The ResourceUrlCleanupRule object

A rule for the URL cleanup rule.

ElementTypeDescription
resourceNamestring

The name of the rule.

regularExpressionstring

The pattern (regular expression) to look for.

replaceWithstring

The text to replace the found pattern with.

The ResourceType object

A rule for the resource type.

ElementTypeDescription
regularExpressionstring

The regular expression to detect the resource.

primaryResourceTypestring

The primary type of the resource.

The element can hold these values
  • CSS
  • IMAGE
  • OTHER
  • SCRIPT
secondaryResourceTypestring

The secondary type of the resource.

Can be null.

Request body JSON model

This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.

json
{ "resourceProviders": [ { "resourceName": "string", "resourceType": "CDN_RESOURCES", "brandIconUrl": "string", "domainNamePatterns": [ "string" ] } ], "resourceUrlCleanupRules": [ { "resourceName": "string", "regularExpression": "string", "replaceWith": "string" } ], "resourceTypes": [ { "regularExpression": "string", "primaryResourceType": "CSS", "secondaryResourceType": "string" } ] }

Response

Response codes

CodeTypeDescription
204-

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

400ErrorEnvelope

Failed. The input is invalid

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.

POSTManaged https://{your-domain}/e/{your-environment-id}/api/config/v1/contentResources/validator
SaaS https://{your-environment-id}.live.dynatrace.com/api/config/v1/contentResources/validator
Environment ActiveGate https://{your-activegate-domain}/e/{your-environment-id}/api/config/v1/contentResources/validator

Authentication

To execute this request, you need an access token with Write configuration (WriteConfig) scope. To learn how to obtain and use it, see Tokens and authentication.

Response

Response codes

CodeTypeDescription
204-

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

400ErrorEnvelope

Failed. The input is invalid

Related topics
  • Configure 3rd-party and CDN content detection

    Learn how to manually define 3rd-party or CDN providers along with auto-detected providers.