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

Exoscale reverse-dns API

Reverse DNS lets you record PTR records for Compute instance public IP addresses or Elastic IPs.

Exoscale reverse-dns API is one of 37 APIs that Exoscale publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Reverse DNS. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and pricing.

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

Requests are made against a single base URL, https://api-{zone}.exoscale.com/v2.

6 operations 2 paths 3 schemas 2 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api-ch-gva-2.exoscale.com/v2
Terms of Service
Resource Areas
1

Paths & Operations 6

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

reverse-dns 6

Reverse DNS lets you record PTR records for Compute instance public IP addresses or Elastic IPs.

GET
/reverse-dns/elastic-ip/{id}
Query the PTR DNS records for an elastic IP
get-reverse-dns-elastic-ip 1 param → 200
POST
/reverse-dns/elastic-ip/{id}
Update/Create the PTR DNS record for an elastic IP
update-reverse-dns-elastic-ip 1 param body → 200
DELETE
/reverse-dns/elastic-ip/{id}
Delete the PTR DNS record for an elastic IP
delete-reverse-dns-elastic-ip 1 param → 200
POST
/reverse-dns/instance/{id}
Update/Create the PTR DNS record for an instance
update-reverse-dns-instance 1 param body → 200
GET
/reverse-dns/instance/{id}
Query the PTR DNS records for an instance
get-reverse-dns-instance 1 param → 200
DELETE
/reverse-dns/instance/{id}
Delete the PTR DNS record for an instance
delete-reverse-dns-instance 1 param → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are operation (5 properties), reverse-dns-record (1 property). Each schema is shown below with its type and property counts.

domain-name
string
reverse-dns-record
object
1 property
operation
object
Operation
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

exoscale-reverse-dns-api-openapi.yml Raw ↑

Other APIs Exoscale publishes across the network.

Exoscale ai-api-key API
Exoscale anti-affinity-group API
Exoscale api-key API
Exoscale block-storage API
Exoscale ccm API
Exoscale cluster API
Exoscale compute API
Exoscale crypto API
Exoscale dbaas API
Exoscale deploy-target API
Exoscale deployment API
Exoscale domain API
Where this information came from

This is an independent, third-party profile of Exoscale reverse-dns 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.