> ## Documentation Index > Fetch the complete documentation index at: https://docs.shoply.gg/llms.txt > Use this file to discover all available pages before exploring further. # List support tickets > The store's tickets, the latest message first. `status` is `open` (the buyer wrote last: Waiting on You on the dashboard), `answered` (the store did) or `resolved`, with `resolvedBy`: `store`, `buyer`, or `auto` (48 hours after the store's reply with no word from the buyer). `lastFrom` and `lastLine` are the latest message's author and first words, `unread` whether the store has opened it since the buyer last wrote, and `orderId` the order it is about, where the buyer picked one. `meta.on` is whether the store takes tickets (off, buyers can open none and the panel shows no Support), and `meta.figures` the dashboard's four: tickets waiting on the store and when the oldest was written, open ones, the average minutes to a first reply over the last 30 days and the 30 before, and how many were resolved in the last 30 days. Needs the `tickets.read` permission (Read Support Tickets). ## OpenAPI ````yaml /api-reference/openapi.json get /stores/{storeId}/support-tickets openapi: 3.1.0 info: title: Shoply API version: '1' description: >- Everything a store's own server can do with a secret API key: its catalogue, orders, customers, marketing, finance and the rest of what the dashboard does. And the Customer API, which a buyer's own device asks with a token of theirs. servers: - url: https://api.shoply.gg/v1 security: - apiKey: [] tags: - name: API key - name: Store - name: Domain - name: Payment methods - name: Analytics - name: Storefronts - name: Storefront code - name: Payment Routing - name: Custom payment methods - name: Products - name: Product pictures - name: Stock - name: Categories - name: Upsells - name: Subscriptions - name: Orders - name: Invoices - name: Reviews - name: Coupons - name: Coupon categories - name: Coupon pop-up - name: Sales - name: Blog - name: Search settings - name: Redirects - name: Sitemap - name: Cart Recovery - name: Email Marketing - name: Email Templates - name: Customers - name: Affiliates - name: Support Tickets - name: Blacklist - name: Fraud protection - name: Disputes - name: Finance - name: Tax - name: Expenses - name: Expense setup - name: API requests - name: Webhook endpoints - name: Webhook deliveries - name: Customer API paths: /stores/{storeId}/support-tickets: get: tags: - Support Tickets summary: List support tickets description: >- The store's tickets, the latest message first. `status` is `open` (the buyer wrote last: Waiting on You on the dashboard), `answered` (the store did) or `resolved`, with `resolvedBy`: `store`, `buyer`, or `auto` (48 hours after the store's reply with no word from the buyer). `lastFrom` and `lastLine` are the latest message's author and first words, `unread` whether the store has opened it since the buyer last wrote, and `orderId` the order it is about, where the buyer picked one. `meta.on` is whether the store takes tickets (off, buyers can open none and the panel shows no Support), and `meta.figures` the dashboard's four: tickets waiting on the store and when the oldest was written, open ones, the average minutes to a first reply over the last 30 days and the 30 before, and how many were resolved in the last 30 days. Needs the `tickets.read` permission (Read Support Tickets). operationId: tickets.list parameters: - name: storeId in: path required: true description: >- The store's ID. A key reaches the store it was made in: `GET /key` answers which. schema: type: string - name: show in: query required: false description: 'Only these: `unresolved` is `open` and `answered` together.' schema: type: string enum: - all - unresolved - open - answered - resolved default: all - name: search in: query required: false description: >- Part of the subject, the buyer's email or the latest message, or the start of the ticket's or the order's ID. schema: type: string - name: page in: query required: false description: Which page of the list. The first is 1. schema: type: integer default: 1 - name: perPage in: query required: false description: How many a page holds, up to 100. schema: type: integer default: 25 responses: '200': description: It worked. content: application/json: schema: type: object properties: success: type: boolean message: nullable: true code: nullable: true data: type: array items: type: object properties: id: type: string email: type: string customerId: nullable: true orderId: type: string subject: type: string status: type: string messages: type: integer pictures: type: integer lastMessageAt: type: string lastFrom: type: string lastLine: type: string unread: type: boolean firstReplyAt: nullable: true answeredAt: nullable: true resolvedAt: nullable: true resolvedBy: nullable: true createdAt: type: string updatedAt: type: string pages: type: integer total: type: integer meta: type: object properties: 'on': type: boolean any: type: boolean figures: type: object properties: waiting: type: integer answered: type: integer open: type: integer oldestWaitingAt: type: string firstReplyMinutes: nullable: true firstReplyMinutesBefore: nullable: true resolved30: type: integer storeOpenLimit: type: integer page: type: integer limits: type: object properties: body: type: integer subject: type: integer picturesPerMessage: type: integer picturesPerTicket: type: integer pictureBytes: type: integer example: success: true message: null code: null data: - id: 8e243e4e-58e7-4d63-a9c3-ef057672a8fd email: grace@example.com customerId: null orderId: bc44febe-0f25-4076-92eb-03a5045a57e7 subject: Key says it is already in use status: open messages: 1 pictures: 0 lastMessageAt: '2026-10-22T16:20:19Z' lastFrom: buyer lastLine: >- I bought Northwind Pro this morning and the key says it is already in use. unread: true firstReplyAt: null answeredAt: null resolvedAt: null resolvedBy: null createdAt: '2026-10-22T16:20:19Z' updatedAt: '2026-10-22T16:20:19Z' pages: 1 total: 1 meta: 'on': true any: true figures: waiting: 1 answered: 0 open: 1 oldestWaitingAt: '2026-10-22T16:20:19Z' firstReplyMinutes: null firstReplyMinutesBefore: null resolved30: 0 storeOpenLimit: 250 page: 1 limits: body: 500 subject: 100 picturesPerMessage: 3 picturesPerTicket: 25 pictureBytes: 5242880 '401': $ref: '#/components/responses/NoKey' '403': $ref: '#/components/responses/NotAllowed' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/TooMany' x-codeSamples: - lang: javascript label: Node.js source: | import Shoply from "@shoplygg/node"; const shoply = new Shoply({ apiKey: process.env.SHOPLY_API_KEY }); const page = await shoply.tickets.list(); // Or every row of every page: for await (const row of shoply.tickets.list()) { console.log(row); } - lang: php label: PHP source: | getenv('SHOPLY_API_KEY')]); $page = $shoply->tickets->list(); // Or every row of every page: foreach ($shoply->tickets->list() as $row) { print_r($row); } - lang: python label: Python source: | import shoply client = shoply.Client() # reads SHOPLY_API_KEY page = client.tickets.list() # Or every row of every page: for row in client.tickets.list(): print(row) components: responses: NoKey: description: >- No API key was sent, or the one sent is not a live key: `api_key_required`, `invalid_api_key`. content: application/json: schema: $ref: '#/components/schemas/Refusal' NotAllowed: description: >- The key is real and may not do this: `missing_scope` (with `requiredScope`), `ip_not_allowed`, `account_unavailable`, or `dashboard_only` for something only a person in the dashboard may do. content: application/json: schema: $ref: '#/components/schemas/Refusal' NotFound: description: >- There is no such thing in this store: `not_found`. A store that is not the key's own is answered the same way. content: application/json: schema: $ref: '#/components/schemas/Refusal' TooMany: description: >- The key has used up its budget for now: `rate_limited`. `Retry-After` says how many seconds to wait. content: application/json: schema: $ref: '#/components/schemas/Refusal' schemas: Refusal: type: object properties: success: type: boolean example: false message: type: string description: What is wrong, in words for a person. code: type: string description: What is wrong, as a word that does not change. data: nullable: true errors: type: object description: >- For `validation_failed`: what is wrong with each field, by the field's name. additionalProperties: type: string required: - success - message - code securitySchemes: apiKey: type: http scheme: bearer description: >- A secret API key, made under Developers in the dashboard: `Authorization: Bearer shoply_sk_...` ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.