Run the Content problems scenario

Launches an asynchronous request to simultaneously run Launch a GREP request and Request content with cURL operations for a URL. It may help you diagnose issues with slow download and high response time. Successful operations return fetched GREP and cURL data.

Query Params
string

For customers who manage more than one account, this runs the operation from another account. The Identity and Access Management API provides a list of available account switch keys.

Body Params

Collects data to use in the Content problems scenario request.

string
length ≥ 1

Unique identifier for an edge server location closest to end users experiencing issues with the URL. Run the List available edge server locations operation to get this value.

string
enum

IP version for the Content problems scenario to use to run cURL and MTR commands, either IPV4 or IPV6.

Allowed:
requestHeaders
array of strings
length ≥ 0

Customized headers for the curl request in the format header: value. The request includes Akamai Pragma headers by default.

requestHeaders
boolean

Runs Content problems from a Site Shield map. To learn more, check Site Shield requests.

sensitiveRequestHeaderKeys
array of strings
length ≥ 0

Sensitive requestHeaders you don't want to store in the database after running the request. Check Sensitive headers to see the list of request headers treated as sensitive by default.

sensitiveRequestHeaderKeys
string
length ≥ 1

IP of the edge server you want to serve traffic from. You can use the ip value from the edgeIps array in the collected diagnostic data.

uri
required

URL you want to run the Content problems scenario for.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json