> ## Documentation Index > Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt > Use this file to discover all available pages before exploring further. # List Helpdesk Tickets > Returns cursor-paginated helpdesk tickets mirrored from the workspace's helpdesk integrations (Zendesk, Pylon, Plain). ## OpenAPI ````yaml GET /v1/helpdesk-tickets openapi: 3.0.0 info: title: Conduit API version: 1.0.0 description: Public API for Conduit. servers: - url: https://api.conduit.ai description: Production security: [] tags: - name: meta description: Discovery and API metadata endpoints. - name: agents description: >- V2 chat agent configuration, including instructions, skills, triggers, and automation behavior. - name: contacts description: >- Contact profile and contact-scoped related resources such as tickets and calls. - name: workspaces description: Workspaces accessible to the current API token. - name: escalations description: >- Chat escalations that require operator review, including message, proposed response, and disposition context when available. - name: conversations description: >- Canonical message threads. Use these endpoints to list threads, inspect conversation state, read transcripts, and send replies. - name: conversation-tags description: >- Conversation labels, root topics, and subtopics used for classification and topic analytics. - name: tickets description: >- Operational queue items tied to conversations, including ticket-scoped transcripts and replies. - name: calls description: Phone call records, transcripts, summaries, and recordings when available. - name: reservations description: >- PMS reservations synced from the workspace's integrations (Hostaway, Guesty, Airbnb, etc.), including guest identity, payment status, and stay dates. - name: appointments description: >- Scheduled appointments (bookings) backed by the Conduit booking service. Exposes allocation context and the upstream booking-service `external_id`. - name: helpdesk_tickets description: >- Helpdesk tickets mirrored from external helpdesk integrations (Zendesk, Pylon, Plain), including requester identity and upstream metadata. - name: kb description: >- Knowledge base search and node management. Nodes represent knowledge base entries (files or directories), chunks are the indexed retrieval units used by search. - name: skills description: >- Workspace agent skills that can be attached to V2 chat agents. Sidebar/global-assistant skills are intentionally excluded. - name: custom_tools description: >- Custom code tools: user-authored Python/JavaScript functions executed in a sandbox when an agent calls them. Includes a runtimes endpoint describing the entrypoint signature, return shape, and available dependencies per language. - name: inbox_types description: >- Workspace inbox types. Each id is stable and usable as a message trigger's `inboxTypeId` and as the `inbox_type_id` filter on list conversations. - name: workflows description: >- Workspace automation workflows: definitions, executions, and per-execution event timelines. - name: insights description: Aggregated workspace analytics, such as conversation automation rate. paths: /v1/helpdesk-tickets: get: tags: - helpdesk_tickets summary: List helpdesk tickets description: >- Returns cursor-paginated helpdesk tickets mirrored from the workspace's helpdesk integrations (Zendesk, Pylon, Plain). Filter by `status`, `channel`, or `connection_id`. operationId: listHelpdeskTickets parameters: - schema: type: string description: Workspace to query. example: j57demo8f8x7c9v0n2q4r6t8y1u3i5o required: true name: workspace_id in: query - schema: type: integer minimum: 1 maximum: 100 description: Page size. Defaults to 20. Max 100. required: false name: limit in: query - schema: type: string description: Pagination cursor returned as `next_cursor` on the previous page. required: false name: cursor in: query - schema: type: string enum: - asc - desc description: Sort direction over last external update time. Defaults to `desc`. required: false name: order in: query - schema: type: string description: >- Filter by helpdesk status. Values depend on the upstream helpdesk system (examples: `open`, `new`, `pending`, `solved`, `closed`). example: open required: false name: status in: query - schema: type: string description: >- Filter by the channel the ticket arrived on (examples: `email`, `web`, `chat`). required: false name: channel in: query - schema: type: string description: >- Filter to tickets from a single helpdesk connection (Zendesk/Pylon/Plain instance). required: false name: connection_id in: query responses: '200': description: Helpdesk tickets content: application/json: schema: type: object properties: data: type: array items: type: object properties: id: type: string workspace_id: type: string contact_id: type: string nullable: true ticket_id: type: string nullable: true description: >- Conduit inbox ticket id when the helpdesk ticket has been linked to a native conversation, otherwise null. connection_id: type: string external_ticket_id: type: string external_group_id: type: string nullable: true external_assignee_id: type: string nullable: true subject: type: string description: type: string nullable: true status: type: string priority: type: string nullable: true type: type: string nullable: true channel: type: string nullable: true tags: type: array items: type: string requester: type: object properties: external_id: type: string name: type: string email: type: string nullable: true required: - external_id - name - email last_external_update_at: type: string created_at: type: string required: - id - workspace_id - contact_id - ticket_id - connection_id - external_ticket_id - external_group_id - external_assignee_id - subject - description - status - priority - type - channel - tags - requester - last_external_update_at - created_at description: >- A helpdesk ticket mirrored from an external helpdesk system (Zendesk, Pylon, Plain). `external_ticket_id` is the upstream ticket id; `id` is the Conduit-stable identifier. next_cursor: type: string nullable: true has_more: type: boolean required: - data - next_cursor - has_more description: Cursor-paginated helpdesk tickets response. example: data: - id: hd77c0dy0mgdpzmqz6tesry8w184002s workspace_id: j57demo8f8x7c9v0n2q4r6t8y1u3i5o contact_id: ph77c0dy0mgdpzmqz6tesry8w184002s ticket_id: tk77c0dy0mgdpzmqz6tesry8w184002s connection_id: cn77c0dy0mgdpzmqz6tesry8w184002s external_ticket_id: zd_12345 external_group_id: grp_42 external_assignee_id: usr_987 subject: Unable to access door code description: Guest reports the keypad is not accepting the code. status: open priority: high type: incident channel: email tags: - urgent - access requester: external_id: zd_user_abc name: Taylor Reid email: taylor.reid@example.com last_external_update_at: '2026-04-19T14:05:00.000Z' created_at: '2026-04-19T13:48:00.000Z' next_cursor: page-token has_more: true '400': description: Invalid request content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '401': description: Unauthorized content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '403': description: Forbidden content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '429': description: Rate limit exceeded content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API Token description: >- Conduit API token. Use `Authorization: Bearer `. Read/write endpoints require a token with write access. ````