Delete a TLS ingest profile

delete

https://{hostname}/api/content-delivery/v1/content-providers/{contentProviderId}/tls-ingest-profiles/{tlsIngestProfileId}

This operation deletes a TLS ingest profile for the specified content provider. A TLS ingest profile can be bound to one or more origins, and can only be deleted if it is not bound to an origin.

Responses

204

The TlsIngestProfile was successfully deleted.

400

An HTTP 400 will be returned if the request could not be processed. For example, if another entity is referring to this entity, and the delete could not be processed.

Language

Credentials

OAuth2

URL

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

403An HTTP 403 will be returned if the principal is not authorized to access the instance of blocklist that the request was made against.

404An HTTP 404 will be returned if the <<resourcePathName | !singularize>> with the specified entityId is not found.

409An HTTP 409 will be returned if the blocklist offered for create/update would lead to a conflicting state.