Skip to main content

3 API limitations blocking AI-driven support automation

  • May 28, 2026 3:08 PM UTC
  • 0 replies
  • 3 views

Forum|alt.badge.img

As AI-powered support workflows become standard, three API gaps are holding teams back: no access to archived tickets, no keyword search, and a hard cap on fetchable tickets. Sharing these as a bundle because they affect the same use case.

 

Hi Freshdesk community 👋

 

We've been building out AI-powered workflows on top of the Freshdesk API — things like automated ticket categorisation, trend analysis, and context retrieval for our AI agents. In doing so, we've run into three limitations that consistently block us (and I suspect many others in the same boat).

I'm sharing these together because they all stem from the same underlying need: comprehensive, flexible programmatic access to ticket data. Happy to hear if others have faced the same issues or found workarounds.
 

Issue 1

Archived tickets are not accessible via the API

Once tickets are archived, they disappear from API responses entirely. For AI use cases — training classification models, auditing historical trends, or giving an AI agent long-term context — this is a significant gap.

Request: Expose archived tickets through the existing tickets endpoint (perhaps behind an include_archived=true parameter) or via a dedicated /archived_tickets endpoint.
 

Issue 2

No keyword search available through the API

The API supports filtering on structured fields (status, assignee, date range, etc.), but there is no way to perform free-text/keyword search across ticket subject lines or descriptions. This makes it impossible to build retrieval pipelines or similarity searches without downloading all tickets first.

Request: Add a query or keyword parameter to the ticket search endpoint that maps to the same full-text search Freshdesk already offers in the UI.
 

Issue 3

Hard limit on the number of tickets fetchable via the API

The current pagination cap makes it impractical to do bulk data pulls for analysis or model training. Any AI use case that needs a representative dataset hits this ceiling quickly.

Request: Either raise (or remove) the pagination limit, or introduce a dedicated data export endpoint / bulk export flow designed for large-scale programmatic access.

 

These three features would make a real difference for teams building AI on top of Freshdesk — and I'd argue they're table-stakes for any support platform positioning itself as AI-ready.

Curious whether others have hit these walls, and whether there are any known workarounds in the meantime. Would also love a 👍 from anyone who'd benefit from seeing these on the roadmap!