# Submit and list feedback tickets

Submit a platform problem report or inquiry ticket and query the status and administrator replies for tickets created by the current authenticated principal. Creation returns the ticket and submitted messages; the personal list returns ticket summaries only.

## Prerequisites

Prepare a personal access token and service address for the target environment as described in [Prepare to call an API](../../api-call-basics.md). Ticket ownership is determined by the authenticated principal; no workspace ID is used in the path, and querying other users' tickets is not supported.

## Call sequence

1. Prepare the problem title, description, expected/actual behavior, reproduction steps, or optional conversation messages, and call [Submit a feedback ticket](../../../../reference/api/genesis/feedback-tickets/create-ticket.md).
2. Save the returned ticket ID and ticket number. If a submission times out with an unknown outcome, check your personal list before retrying to avoid duplicate tickets.
3. Paginate through [List my feedback tickets](../../../../reference/api/genesis/feedback-tickets/list-my-tickets.md) to track ticket status and administrator replies.

## API operations

| Task | API operation | When to use it or what to check |
| --- | --- | --- |
| Submit a platform feedback ticket | [Submit a feedback ticket](../../../../reference/api/genesis/feedback-tickets/create-ticket.md) | Submit an issue description and obtain a ticket ID and number. |
| List tickets submitted by the current account | [List my feedback tickets](../../../../reference/api/genesis/feedback-tickets/list-my-tickets.md) | Track handling status and administrator replies, or confirm creation after a timeout. |

## Confirm the result

After creation, verify the returned ticket number and initial status. When listing tickets, paginate using `limit` and `offset` until all `total` items are read or the returned list is empty.

## Limitations and notes

Personal ticket lists support `limit` and `offset` pagination only; administrator status/account filters and individual ticket conversation retrieval endpoints require platform administrator privileges.
