Zendesk (via Apideck Proxy)

Access Zendesk through Apideck's Proxy API with managed Vault auth. Apideck stores credentials, refreshes tokens, and forwards your HTTP calls to Zendesk's native API — you keep using Zendesk's own request and response shapes, while Apideck eliminates per-tenant credential plumbing and gives you a single auth integration shared across every Apideck connector.

Auth-only / proxy-only connector. Apideck does not map Zendesk to a unified-API resource model — your code talks Zendesk's own API directly through the Proxy. You still get Vault credential storage, token refresh, retries, and a consistent request envelope.

Quick facts

• Apideck serviceId: zendesk
• Mode: Proxy-only (no unified API resources)
• Auth type: oauth2
• Status: beta
• Gotchas: page
• Zendesk docs: https://developer.zendesk.com/api-reference/
• Homepage: https://www.zendesk.com/

When to use this skill

Activate this skill when the user wants to call Zendesk via Apideck — for example, "call the Zendesk API" or "fetch data from Zendesk". This skill teaches the agent: