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

Bunny.net DNSZones API

The DNSZones API from Bunny.net — 6 operation(s) for dnszones.

Bunny.net DNSZones API is one of 26 APIs that Bunny.net publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include DNS Zones. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 10 operations across 6 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.bunny.net.

10 operations 6 paths 2 schemas 2 DELETE2 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.bunny.net
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

Bunny.net DNSZones API declares 1 security scheme for authenticating requests. An API key is passed in the header as AccessKey (accessKeyAuth). By default, every request must be authenticated.

  • accessKeyAuth — API key issued from the Bunny.net dashboard.

Paths & Operations 10

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

DNSZones 10
GET
/dnszone
List DNS zones
listDnsZones → 200
POST
/dnszone
Add DNS zone
addDnsZone body → 201
GET
/dnszone/{id}
Get DNS zone
getDnsZone 1 param → 200
POST
/dnszone/{id}
Update DNS zone
updateDnsZone 1 param body → 204
DELETE
/dnszone/{id}
Delete DNS zone
deleteDnsZone 1 param → 204
POST
/dnszone/{id}/records
Add DNS record
addDnsRecord 1 param body → 201
POST
/dnszone/{id}/records/{recordId}
Update DNS record
updateDnsRecord 2 params body → 204
DELETE
/dnszone/{id}/records/{recordId}
Delete DNS record
deleteDnsRecord 2 params → 204
POST
/dnszone/{id}/enableDNSSEC
Enable DNSSEC
enableDnssec 1 param → 204
POST
/dnszone/{id}/disableDNSSEC
Disable DNSSEC
disableDnssec 1 param → 204

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are DnsRecord (13 properties), DnsZone (9 properties). Each schema is shown below with its type and property counts.

DnsRecord
object
13 properties
DnsZone
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bunny-net-dnszones-api-openapi.yml Raw ↑

Other APIs Bunny.net publishes across the network.

Bunny.net Core Platform API
Bunny.net Pull Zones API
Bunny.net Storage Zones API
Bunny.net Edge Storage API
Bunny.net DNS API
Bunny.net Stream API
Bunny.net Stream Webhooks
Bunny.net Shield API
Bunny.net Optimizer
Bunny.net Scripting / Edge Compute API
Bunny.net Purge API
Bunny.net Statistics API
Where this information came from

This is an independent, third-party profile of Bunny.net DNSZones 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.