The API Report CardAPI Index
Zendesk Sell

Zendesk Sell API

Sales CRM / Pipeline & Deal Management · zendesk.com

Zendesk Sell offers a self-serve REST API with Core CRUD, delta Sync, a Firehose event stream, and Search, under OAuth 2.0 or instant personal tokens. The practical cap of 1,000 requests per hour per account bites quickly, and the API still runs on the legacy api.getbase.com domain.

Last verified: October 2026Marketing & SalesNO MCP
API GRADE
C+
VERIFIED OCT 2026

SCORECARD

ExistenceGOODSelf-serve REST API with four surfaces: Core CRUD, delta Sync, a Firehose event stream, and Search.
AccessGOODPersonal access tokens are generated from the dashboard with no approval step; multi-user apps register for OAuth.
CoverageMIXEDCore CRUD plus Sync and Firehose cover Sell objects end to end; Support data lives on a separate Zendesk API.
AuthMIXEDOAuth 2.0 for multi-user apps; single-user personal tokens have infinite lifetime and password-grant is still supported.
Docs & DXMIXEDReference lives on developer.zendesk.com, but there is no Sell sandbox; personal tokens are the testing path.
StabilityMIXEDStill served from the legacy api.getbase.com domain; sliding-window rate limits break naive retry logic.
MCPNONENo official or community MCP server was found for the Zendesk Sell CRM API. Searches of GitHub, npm, and Zendesk developer resources surfaced nothing covering Sell. VERIFIED 2026-08
MORE FROM THE REPORT CARD
Supergood turns hard-to-integrate enterprise software into clean REST APIs and MCP tools: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Zendesk Sell scores C+ on Supergood's API Report Card. Zendesk Sell offers a self-serve REST API with Core CRUD, delta Sync, a Firehose event stream, and Search, under OAuth 2.0 or instant personal tokens. The practical cap of 1,000 requests per hour per account bites quickly, and the API still runs on the legacy api.getbase.com domain.

Tried to integrate with Zendesk Sell?
SOURCES
Per-account rate limit of 1,000 requests/hour with secondary 200/10-min and 50/min limits is widely cited as a sync killer; most integrators hit it in their first week aeroleads.com ↗
Sliding-window rate-limit algorithm (not a clean hourly reset) confuses developers and breaks naive retry/backoff strategies aeroleads.com ↗
Endpoint cost is non-uniform, fetching a deal with related contacts and activities can consume 3–5 requests against the quota aeroleads.com ↗
Documented headline limit (36,000/hr, 10/sec/token) is reachable in theory but the practical per-account cap is much lower developer.zendesk.com ↗
API still served from api.getbase.com (legacy Base CRM domain) rather than a Zendesk-branded endpoint, signaling limited platform investment developer.zendesk.com ↗
Sell API is a separate surface from the Zendesk Support API, developers integrating both products manage two auth flows, two rate-limit pools, and two SDK ecosystems developer.zendesk.com ↗
Higher rate limits require contacting Zendesk and often a plan upgrade rather than a self-serve quota increase developer.zendesk.com ↗
Recurring sign-in/login failures and confused first-line support handling them trustradius.com ↗
Inability to cancel via phone or email, customers report being charged $59/mo for three months after asking to cancel trustradius.com ↗
UI glitches that interrupt workflow and hurt rep productivity trustradius.com ↗
Positioned/priced as a peer of Salesforce/HubSpot but functionality is closer to entry-level, best fit only for sub-15-person teams elevatiq.com ↗
Contact data does not sync between Sell and Zendesk Support by default, the unified-context promise requires extra integration work factbranch.com ↗
Bundled with the broader Zendesk product, which has seen its own pricing/license backlash on G2 and Reddit g2.com ↗
Smaller third-party app ecosystem than Salesforce AppExchange or HubSpot Marketplace, limiting plug-and-play integrations cloudtalk.io ↗