List tickets with the Freshdesk API

Lists tickets, newest first by default. Without updated_since only tickets created in the last 30 days come back, and spam or deleted tickets only come with filter. Pages are numbered from 1, up to page 300; a page with fewer tickets than per_page is the last one.

Identifier
freshdesk_list_tickets

The request

POST https://connect.reportei.com/api/tools/freshdesk_list_tickets/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "filter": "new_and_my_open"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
filterstringNoPredefined view: new and open tickets of the agent, tickets the agent watches, spam or deleted tickets.Values: new_and_my_open, watching, spam, deleted
requester_idintegerNoOnly the tickets of this requester: the id of a contact from List contacts, or the requester_id of a ticket.
emailstringNoOnly the tickets of the requester with this email address.
unique_external_idstringNoOnly the tickets of the requester with this external id, the id of the requester in your own system.
company_idintegerNoOnly the tickets of this company, from Search companies.
updated_sincestringNoOnly tickets updated at or after this UTC time, for example 2026-10-01T00:00:00Z. Use it to reach tickets older than 30 days.
order_bystringNoSort field. The default is created_at.Values: created_at, due_by, updated_at, status
order_typestringNoSort order. The default is desc.Values: asc, desc
includestringNoComma-separated extras for each ticket: stats (closed, resolved and first response times), requester (email, id, mobile, name and phone) and description. Each one costs 2 more API credits per call.
pageintegerNoPage number, starting at 1.
per_pageintegerNoTickets per page, up to 100. The default is 30.

Supported connections

Your customer connects their Freshdesk account once, with one of the modes below. The same connection serves every tool of the toolkit.

Username and password

Your customer enters the app credentials on a Connect screen, or your system sends them with POST /api/customer-toolkits, with no screen.

When connecting, your customer also enters {domain}: the address of their account on the app's API.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/freshdesk_list_tickets. It becomes your agent's tool definition with no conversion.

Other Freshdesk tools

See all 13 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.