The connection’s listings, most recently changed first
const url = 'https://api.crossmart.io/api/v1/workspaces/example/channel-connections/example/listings?status=PENDING&limit=25';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://api.crossmart.io/api/v1/workspaces/example/channel-connections/example/listings?status=PENDING&limit=25'Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”1-based page number, for tables with page numbers. It wins over cursor.
Responses
Section titled “Responses”object
object
How the product joined the store: by hand, by an import, or by the automatic rule
The product’s id on the channel
Where to see it on the channel
Why the last sync failed
What the channel refused the last publish for lacking (such as item_specifics), when the merchant can add it; null otherwise
The channel category it is listed in, on channels with categories (eBay)
object
The category with its ancestors, as the channel shows it
The product on this store, in one state computed by the server: draft (not selected for the store), needs_details (selected, but the store setup or the product lacks something publishing needs), ready (publishable, not sent yet), publishing (queued or in flight), published, failed, removing (being taken off) or removed.
For needs_details and failed: a short, merchant-readable reason (what to add, or the channel’s message). Never holds secrets. Null for the other states.
How many match in all, for page numbers
Example
{ "items": [ { "status": "PENDING", "source": "MANUAL", "missingRequirement": "reconnect", "category": { "id": "20625", "name": "Home & Garden > Kitchen, Dining & Bar > Dinnerware & Serving Dishes > Mugs" }, "displayState": "draft", "displayReason": "Choose a shipping policy in this eBay connection’s listing defaults." } ]}