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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Engineering Platform

APIs.io Engineering Platform WHOIS Record API

The WHOIS Record API from APIs.io Engineering Platform — 1 operation(s) for whois record.

Documentation Provider Profile APIs.io OpenAPI GitHub

This API exposes 1 operation across 1 path, and defines 8 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.

1 operations 1 paths 8 schemas 1 GET

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
License
BSD-3-Clause
Resource Areas
1

Authentication & Security 4

APIs.io Engineering Platform WHOIS Record 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 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

WHOIS Record 1
GET
/accounts/{account_id}/intel/whois
APIs.io Engineering Platform Get WHOIS Record
whois-record-get-whois-record 2 params → 4XX200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are cloudforce-one_whois (87 properties), cloudforce-one_api-response-common-failure (4 properties), cloudforce-one_api-response-common (3 properties). Each schema is shown below with its type and property counts.

cloudforce-one_identifier
string
Identifier
cloudforce-one_messages
array
cloudforce-one_api-response-single
object
cloudforce-one_whois
object
87 properties 8 required
cloudforce-one_domain_name
string
cloudforce-one_api-response-common
object
3 properties 3 required
cloudforce-one_schemas-single_response
cloudforce-one_api-response-common-failure
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

engineering-platform-whois-record-api-openapi.yml Raw ↑
#WHOIS Record
← Back to A APIs
API Details
ID
engineering-platform:engineering-platform-whois-record-api
Base URL
https://api.cloudflare.com/client/v4
Docs
https://developers.cloudflare.com/api/
Provider
Engineering Platform
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=engineering-platform-whois-record-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/engineering-platform-whois-record-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of APIs.io Engineering Platform WHOIS Record 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.