Origin TLS Client Auth

origin_tls_client_auth

Methods

Upload Certificate -> Envelope<>
post/zones/{zone_id}/origin_tls_client_auth

Upload your own certificate you want Cloudflare to use for edge-to-origin communication to override the shared certificate. Please note that it is important to keep only one certificate active. Also, make sure to enable zone-level authenticated origin pulls by making a PUT call to settings endpoint to see the uploaded certificate in use.

Delete Certificate -> Envelope<>
delete/zones/{zone_id}/origin_tls_client_auth/{certificate_id}

Delete Certificate

Get Certificate Details -> Envelope<>
get/zones/{zone_id}/origin_tls_client_auth/{certificate_id}

Get Certificate Details

List Certificates -> SinglePage<>
get/zones/{zone_id}/origin_tls_client_auth

List Certificates

Domain types

ZoneAuthenticatedOriginPull = { id, certificate, expires_on, 4 more... }

origin_tls_client_auth.hostnames

Methods

Get The Hostname Status For Client Authentication -> Envelope<>
get/zones/{zone_id}/origin_tls_client_auth/hostnames/{hostname}

Get the Hostname Status for Client Authentication

Enable Or Disable A Hostname For Client Authentication -> Envelope<Array<>>
put/zones/{zone_id}/origin_tls_client_auth/hostnames

Associate a hostname to a certificate and enable, disable or invalidate the association. If disabled, client certificate will not be sent to the hostname even if activated at the zone level. 100 maximum associations on a single certificate are allowed. Note: Use a null value for parameter enabled to invalidate the association.

Security
API Email + API Key

The previous authorization scheme for interacting with the Cloudflare API, used in conjunction with a Global API key.

Example: X-Auth-Email: user@example.com

The previous authorization scheme for interacting with the Cloudflare API. When possible, use API tokens instead of Global API keys.

Example: X-Auth-Key: 144c9defac04969c7bfad8efaa8ea194

Parameters
zone_id: string

Identifier

Response fields
errors: Array<>
messages: Array<>
success: true

Whether the API call was successful

result: Array<>
Optional
result_info: { count, page, per_page, 1 more... }
Optional
Request example
200Example

Domain types

AuthenticatedOriginPull = { cert_id, cert_status, cert_updated_at, 11 more... }

origin_tls_client_auth.hostnames.certificates

Methods

Upload A Hostname Client Certificate -> Envelope<{ id, certificate, expires_on, 5 more... }>
post/zones/{zone_id}/origin_tls_client_auth/hostnames/certificates

Upload a certificate to be used for client authentication on a hostname. 10 hostname certificates per zone are allowed.

Delete Hostname Client Certificate -> Envelope<{ id, certificate, expires_on, 5 more... }>
delete/zones/{zone_id}/origin_tls_client_auth/hostnames/certificates/{certificate_id}

Delete Hostname Client Certificate

Get The Hostname Client Certificate -> Envelope<{ id, certificate, expires_on, 5 more... }>
get/zones/{zone_id}/origin_tls_client_auth/hostnames/certificates/{certificate_id}

Get the certificate by ID to be used for client authentication on a hostname.

List Certificates -> SinglePage<>
get/zones/{zone_id}/origin_tls_client_auth/hostnames/certificates

List Certificates

Domain types

Certificate = { id, certificate, expires_on, 5 more... }

origin_tls_client_auth.settings

Methods

Get Enablement Setting For Zone -> Envelope<{ enabled }>
get/zones/{zone_id}/origin_tls_client_auth/settings

Get whether zone-level authenticated origin pulls is enabled or not. It is false by default.

Set Enablement For Zone -> Envelope<{ enabled }>
put/zones/{zone_id}/origin_tls_client_auth/settings

Enable or disable zone-level authenticated origin pulls. 'enabled' should be set true either before/after the certificate is uploaded to see the certificate in use.