Wish Tickets API
For each consumer question or complaint, a ticket is created to manage the dialogue between you, Wish, and the consumer. With this API, you can fetch tickets awaiting your response, fetch a specific ticket, close a ticket, and reply to tickets.
Wish Tickets API is one of 21 APIs that Wish publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Tickets. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.
This API exposes 4 operations across 3 paths, and defines 10 schemas. It is described by OpenAPI 3.0.0, at version 3.0.65.
Requests are made against a single base URL, https://merchant.wish.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Wish Tickets API declares
2 security schemes
for authenticating requests.
It supports OpenID Connect (OpenID) discovered at https://merchant.wish.com/oidc/.well-known/openid-configuration.
It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 37 scopes.
By default, every request must be authenticated.
Paths & Operations 4
Across 3 paths, the API surfaces 4 operations — 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
For each consumer question or complaint, a ticket is created to manage the dialogue between you, Wish, and the consumer. With this API, you can fetch tickets awaiting your respons…
Schemas 10
The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Ticket (14 properties), Reply (4 properties), ReplySupportingFile (2 properties), APIError (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Wish 12
Other APIs Wish publishes across the network.