> ## 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 Contact Tickets > Retrieve all tickets associated with a specific contact. ## OpenAPI ````yaml GET /v1/contacts/{id}/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. paths: /v1/contacts/{id}/tickets: get: tags: - contacts summary: List tickets for a contact description: >- Convenience endpoint that filters the ticket queue down to tickets for a single contact. operationId: listContactTickets parameters: - schema: type: string description: Contact id. example: ph77c0dy0mgdpzmqz6tesry8w184002s required: true name: id in: path - schema: type: string description: >- Optional workspace override. If omitted, Conduit resolves the contact's workspace automatically. example: j57demo8f8x7c9v0n2q4r6t8y1u3i5o required: false name: workspace_id in: query - schema: type: integer minimum: 1 maximum: 100 required: false name: limit in: query - schema: type: string required: false name: cursor in: query - schema: type: string enum: - asc - desc required: false name: order in: query - schema: type: string enum: - open - new - pending - resolved - closed description: '`open` returns actionable tickets (`new` + `pending`).' required: false name: status in: query - schema: type: string enum: - team - customer - third_party - none required: false name: waiting_on in: query - schema: type: string required: false name: channel in: query responses: '200': description: Contact 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 conversation_id: type: string channel: type: string status: type: string enum: - new - pending - resolved - closed waiting_on: type: string nullable: true inbox_type_id: type: string subject: type: string nullable: true summary: type: string nullable: true ai_paused: type: boolean assignee: type: object nullable: true properties: id: type: string name: type: string email: type: string picture_url: type: string nullable: true required: - id - name - email - picture_url follow_up_at: type: string nullable: true last_message_at: type: string nullable: true last_message_preview: type: string nullable: true created_at: type: string updated_at: type: string call_transcript_id: type: string nullable: true required: - id - workspace_id - contact_id - conversation_id - channel - status - waiting_on - inbox_type_id - subject - summary - ai_paused - assignee - follow_up_at - last_message_at - last_message_preview - created_at - updated_at - call_transcript_id next_cursor: type: string nullable: true has_more: type: boolean required: - data - next_cursor - has_more description: Cursor-paginated tickets response. example: data: - id: xd88mkfbmxgckpeyzs8m9r9d3d843me3 workspace_id: j57demo8f8x7c9v0n2q4r6t8y1u3i5o contact_id: ph77c0dy0mgdpzmqz6tesry8w184002s conversation_id: ph77c0dy0mgdpzmqz6tesry8w184002s channel: unthreaded_email status: new waiting_on: customer inbox_type_id: guest subject: Early check-in request summary: >- Guest asked to confirm whether early arrival is possible. ai_paused: false assignee: id: m48k3v7p2q9x5t1w8r6n4j0y3u2i5o7a name: Alex M email: alex@example.com picture_url: null follow_up_at: null last_message_at: '2026-04-03T03:14:15.000Z' last_message_preview: Can I check in early? created_at: '2026-04-01T17:22:10.000Z' updated_at: '2026-04-03T03:14:15.000Z' call_transcript_id: null 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 '404': description: Not found 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. ````