Create a new TLS delivery profilepost https://{hostname}/api/content-delivery/v1/content-providers/{contentProviderId}/tls-delivery-profilesPath ParamscontentProviderIdintegerrequiredBody ParamscontentProviderIdintegerrequired≥ 1namestringrequiredlength between 1 and 128descriptionstringlength ≤ 256caCertificatestringlength ≤ 10000caCertificateSecretIdstringenableClientAuthbooleanDefaults to falsetruefalsecrlstringlength ≤ 10000tlsCertificatestringlength ≤ 10000tlsCertificateKeystringlength ≤ 10000tlsCertificateAndKeySecretIdstringtlsBufferSizeintegerenum41632Allowed:41632ecdhCurvestringenumSECP384R1PRIME256V1Allowed:SECP384R1PRIME256V1tlsVerificationDepthinteger1 to 10ciphersstringlength ≤ 65535Responses 201An HTTP 201 will be returned if the request is successfully processed, and a new tls-delivery-profile object is created. The location of the new object will be specified in the location header. 400An HTTP 400 will be returned if the request is badly formed or has constraint violations 403An HTTP 403 will be returned if the principal is not authorized to access the instance of blocklist that the request was made against. 409An HTTP 409 will be returned if the blocklist offered for create/update would lead to a conflicting state.Updated about 2 months ago