List My Requests
list_requestsRead-onlyIdempotent
List and search the requests the signed-in user submitted, newest first, with number, subject, status and solvability. Use it to review your own tickets, not an agent queue.
Instructions
List the requests the signed-in user submitted, newest activity first by default. Returns each request with its number, subject, status and whether the user can mark it solved; pass a query to search their own requests by free text instead of listing all of them. Scoped to the caller by Zendesk itself — it can never return anyone else's tickets — which is why an agent calling this sees only requests they raised, not their queue. Use get_request to read one with its full conversation. Agents wanting a queue want list_tickets, search_tickets or get_view_tickets instead.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page number for offset pagination. Increment it while keeping `per_page` fixed to fetch subsequent pages; page 1 is the first page. | |
| query | No | Free text to match against the caller's own requests. When given, the search endpoint is used instead of the plain listing; omit it to list everything. | |
| status | No | Restrict to these ticket states, e.g. ["open","pending"] for anything still being worked. Validated here because Zendesk silently returns every request when it does not recognise a status. | |
| sort_by | No | Which timestamp orders the results: updated_at surfaces recent activity, created_at the newest submissions. | updated_at |
| per_page | No | Number of results per page for offset pagination (1-100). Pair with `page` to walk large result sets; the response header reports the total count and whether more pages remain. | |
| sort_order | No | Direction of that ordering; desc puts the most recent first, which is what a user following their tickets wants. | desc |