Zendesk Support Addresses API is one of 150 APIs that Zendesk publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 2 JSON Schema definitions.
Tagged areas include Support Addresses. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 2 JSON Schemas.
This API exposes
6 operations
across 3 paths,
and defines 2 schemas.
It is described by OpenAPI 3.1.0, at version 1.0.
Requests are made against the base URL https://{subdomain}.zendesk.com.
6 operations3 paths2 schemas1 DELETE2 GET1 POST2 PUT
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.1.0
API Version
1.0
Base URL
https://{subdomain}.zendesk.com
Resource Areas
1
Paths & Operations 6
Across 3 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
Support Addresses 6
GET
/api/v2/recipient_addresses
Zendesk Get Api V2 Recipientaddresses
ListSupportAddresses→ 200
POST
/api/v2/recipient_addresses
Zendesk Post Api V2 Recipientaddresses
CreateSupportAddress→ 201
GET
/api/v2/recipient_addresses/{support_address_id}
Zendesk Get Api V2 Recipientaddresses Supportaddressid
ShowSupportAddress1 param→ 200
PUT
/api/v2/recipient_addresses/{support_address_id}
Zendesk Put Api V2 Recipientaddresses Supportaddressid
UpdateSupportAddress1 param→ 200
DELETE
/api/v2/recipient_addresses/{support_address_id}
Zendesk Delete Api V2 Recipientaddresses Supportaddressid
Zendesk Put Api V2 Recipientaddresses Supportaddressid Verify
VerifySupportAddressForwarding1 param→ 200
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are SupportAddressesResponse (1 property), SupportAddressResponse (1 property). Each schema is shown below with its type and property counts.
SupportAddressResponse
object
1 property
SupportAddressesResponse
object
1 property
Specification
The full machine-readable OpenAPI contract behind this narrative.
