Freshdesk

REST API at {domain}.freshdesk.com/api/v2/ with standard CRUD operations. Tickets support create, update, delete, list (with filters), and reply operations. Ticket filters can query by status, priority, agent, group, type, and custom fields. Conversations (ticket replies and notes) are nested under tickets. Contact and company management follows conventional patterns. The API design is clean and consistent — simpler than Zendesk's larger surface. Pagination uses page-based pagination (page and per_page parameters) — less efficient than cursor-based for large datasets. Bulk operations for tickets (update, delete) are available. The API doesn't support real-time events via WebSocket — agents must use webhooks or polling. Search uses Freshdesk's query language.

API errors return JSON with description and errors[] array. HTTP status codes follow conventions: 400 for bad requests, 401 for auth, 404 for not found, 429 for rate limits. Rate limits are plan-dependent: 50/minute on free, 200/minute on Growth, 400/minute on Pro, 700/minute on Enterprise. This is tighter than some competitors, especially on lower plans — agents doing bulk operations must throttle carefully. The 429 response includes Retry-After header. Webhook delivery for automations is fire-and-forget — no retry on failure, which agents must account for. Bulk ticket operations are synchronous (not async/polling), which means timeouts are possible on large batches. Error messages are generally clear but field-level validation errors could be more specific.

Freshdesk provides core helpdesk functionality — ticketing, knowledge base, canned responses, automations, and multi-channel support (email, phone, chat, social) — at a lower price point than Zendesk. For agents, the REST API covers ticket CRUD, contact management, knowledge base articles, and basic reporting. The free tier (up to 10 agents) makes Freshdesk accessible for smaller teams and testing. Automations (Dispatch'r, Supervisor, Observer) handle rule-based ticket routing and escalation. The Freshworks suite (Freshsales, Freshservice, Freshchat) shares a common platform, enabling cross-product data flows. Main limitations versus Zendesk: less extensible custom object model, fewer marketplace integrations, and smaller developer ecosystem. For straightforward helpdesk automation agents, Freshdesk's simplicity is an advantage.

API authentication uses API key as username with Basic Auth (password field is 'X' — ignored). API keys are generated per-agent in the Freshdesk profile. Keys have the same permissions as the agent's role — admin keys have full access, agent keys are limited to their assigned tickets and groups. This role-inheriting model is more granular than platforms that issue single-scope API tokens. No OAuth for third-party apps (Freshdesk Marketplace uses a different auth mechanism). SSL is enforced. IP whitelisting available on higher plans. No temporary credential mechanism. For agents, the key-per-agent model works well for single-tenant deployments but lacks programmatic credential management for scaling.

API documentation at developers.freshdesk.com is straightforward — endpoint reference with parameters, response examples, and curl commands. The documentation is less voluminous than Zendesk's but covers the core API well. Code examples are primarily curl-based; language-specific SDK documentation is thinner. Community SDKs exist for Python, Ruby, and Node but vary in maintenance status — no official SDKs from Freshworks for Freshdesk specifically. Integration guides for common platforms (Slack, Salesforce, JIRA) are available. The developer community is smaller than Zendesk's. Freshworks developer portal covers cross-product integration patterns. For agents with straightforward ticket automation needs, the documentation surface is manageable and sufficient.