How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

APIs.io Engineering Platform Access mTLS Authentication API

The Access mTLS Authentication API from APIs.io Engineering Platform — 3 operation(s) for access mtls authentication.

This API exposes 7 operations across 3 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 4.0.0.

Requests are made against the base URL https://api.cloudflare.com/client/v4.

7 operations 3 paths 18 schemas 1 DELETE3 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4.0.0
Base URL
https://api.cloudflare.com/client/v4
Authentication
API Key, API Key, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 4

APIs.io Engineering Platform Access mTLS Authentication API declares 4 security schemes for authenticating requests. An API key is passed in the header as X-Auth-Email (api_email). An API key is passed in the header as X-Auth-Key (api_key). It accepts HTTP bearer tokens (api_token). An API key is passed in the header as X-Auth-User-Service-Key (user_service_key).

Paths & Operations 7

Across 3 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Access mTLS Authentication 7
GET
/accounts/{account_id}/access/certificates
APIs.io Engineering Platform List mTLS certificates
access-mtls-authentication-list-mtls-certificates 1 param → 4XX200
POST
/accounts/{account_id}/access/certificates
APIs.io Engineering Platform Add an mTLS certificate
access-mtls-authentication-add-an-mtls-certificate 1 param body → 4XX201
DELETE
/accounts/{account_id}/access/certificates/{certificate_id}
APIs.io Engineering Platform Delete an mTLS certificate
access-mtls-authentication-delete-an-mtls-certificate 2 params → 4XX200
GET
/accounts/{account_id}/access/certificates/{certificate_id}
APIs.io Engineering Platform Get an mTLS certificate
access-mtls-authentication-get-an-mtls-certificate 2 params → 4XX200
PUT
/accounts/{account_id}/access/certificates/{certificate_id}
APIs.io Engineering Platform Update an mTLS certificate
access-mtls-authentication-update-an-mtls-certificate 2 params body → 4XX200
GET
/accounts/{account_id}/access/certificates/settings
APIs.io Engineering Platform List all mTLS hostname settings
access-mtls-authentication-list-mtls-certificates-hostname-settings 1 param → 4XX200
PUT
/accounts/{account_id}/access/certificates/settings
APIs.io Engineering Platform Update an mTLS certificate's hostname settings
access-mtls-authentication-update-an-mtls-certificate-settings 1 param body → 4XX202

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are access_certificates (7 properties), access_api-response-common-failure (4 properties), access_result_info (4 properties), access_api-response-common (3 properties). Each schema is shown below with its type and property counts.

access_settings
object
3 properties 3 required
access_uuid
string
UUID
access_response_collection_hostnames
access_certificates
object
7 properties
access_components-schemas-id_response
access_certificates_components-schemas-name
string
The name of the certificate.
access_api-response-common-failure
object
4 properties 4 required
access_fingerprint
string
The MD5 fingerprint of the certificate.
access_certificates_components-schemas-single_response
access_result_info
object
4 properties
access_api-response-common
object
3 properties 3 required
access_timestamp
string
access_api-response-single
object
access_messages
array
access_identifier
string
Identifier
access_associated_hostnames
array
The hostnames of the applications that will use this certificate.
access_certificates_components-schemas-response_collection
access_api-response-collection
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

engineering-platform-access-mtls-authentication-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of APIs.io Engineering Platform Access mTLS Authentication API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.