|Headers allowed in a request.|
HTTP methods allowed for sending a request. The allowed methods vary based on resource and resource type.
For more information about which methods the different resource types support, see Reference.
|Domains from which requests are accepted in cross-origin resource sharing (CORS).|
|Caching behavior that client applications and other caching mechanisms along the request/response chain must follow.||Control options for the current connection.|
|Content encoding (compression) applied to the response body.|
|Media type of the response body.|
|Date and time at which the response was sent.|
|Information about the server software that handled the request and sent the response.|
|HTTP Strict Transport Security (HSTS) policy specifying for how long (in seconds) the client application should access the server only through secure HTTPS connections.|
|Transfer encoding applied to the response body to safely transmit it over the network to the client application.|
|Prevents browsers from MIME-sniffing the response body away from the media type declared in the |
|Specifies whether the client application is allowed to render the response body in a frame (a ||Server-side technology on which the service runs.|
|Specifies whether and what type of cross-site scripting (XSS) protection is enabled for the browser.|
For more information about the standard HTTP headers, see the header fields registry maintained by IANA.
All responses use the JSON format for the body.
A single resource is returned as an object. The following example shows a user object.
|The server successfully processed the request. The response includes the associated resource data.|
|The server successfully deleted the target resource. The response does not include any resource data.|
|The server could not process the request due to an error in the request.||Check that the request uses the correct URL, includes the necessary headers, and, in case of a POST or PUT request, contains a valid JSON body.|
|The server could not authenticate the request because the access token is invalid or missing.||Check that the request includes a valid access token.|
|The server successfully authenticated the request, but could not authorize access to the target resource because the access token does not grant sufficient permission.||Check that you're targeting a resource or resources that you have access to.|
|The server could not find the requested resource.||Check that you're using the correct resource IDs.|
The server could not process the request because the target resource failed to fulfill one or more preconditions.
This status code only applies to DELETE requests to
|If you want to delete the content template, first remove it from all modifications.|