Update Trusted State of Content Object

PUT 
/api/content/:contentType/:key/trusted

Update the trusted state of a content object. This is critical for links and files that may harm the application. The trusted state can only be changed by your application-wide ADMINs.

You can find more information about content management here.

Note: You have to specify the content type. For articles it is articles.

Locale

A locale can be specified for this request. The email will be sent in the specified locale. You can learn more about locale in emails here.

If no locale is specified, the applications default locale will be used. You can learn more about configuring the default locale here.

Tokens

• A valid AccessToken with ADMIN permissions on the server.

Request

Responses

200

The updated content object. The response depends on the content object. For articles it will return FullArticleResponse.

401

The following error codes correspond to this status:

• ACCESS_TOKEN_EXPIRED: Indicates that the access token is expired.
• ACCESS_TOKEN_INVALID: Indicates that the access token cannot be decoded.
• AUTHENTICATION_REQUIRED: User is not authenticated.

403

The following error codes correspond to this status:

• ROLE_REQUIRED: Principal does not have required role.

404

The following error codes correspond to this status:

• CONTENT_TYPE_NOT_FOUND: Content type not found.
• CONTENT_NOT_FOUND: Content not found.

500

The following error codes correspond to this status:

• ACCESS_TOKEN_ALLOWLIST_READING_FAILURE: Represents an exception indicating a failure when reading the allowlist for an access token cache.
• DATABASE_FAILURE: Exception representing a general failure related to database operations.
• RESPONSE_MAPPING_ERROR: Failed to map response.