Skip to main content
DELETE
Delete one of your accounts listings

Autorizaciones

Authorization
string
header
requerido

Your API key, from the cabinet under Seller → API keys.

Parámetros de ruta

id
string<uuid>
requerido

Respuesta

OK

How a listing sold by hand promises to hand over.

id
string<uuid>
title
string
description
string
attributes
object

The category's own fields, keyed by the schema's key.

tags
string[]
status
enum<string>

draft on create, then active once you publish it; unpublish takes it back to draft. archived is yours too, through DELETE. sold follows an order: the last unit went to a closed one. changes_requested is moderation sending a live listing back: it is off the marketplace, moderation_reason_code says why, and your next PATCH makes it a draft to publish again.

Opciones disponibles:
draft,
active,
changes_requested,
sold,
archived
created_at
string<date-time> | null
updated_at
string<date-time> | null
published_at
string<date-time> | null

When publish put it on the marketplace. null while it is a draft, and written once — pausing and unpausing leave it alone.

moderation_reason_code
enum<string> | null

Why moderation asked for changes. Kept through the PATCH that makes the listing a draft, null once it is published again.

Opciones disponibles:
prohibited_item,
misleading_description,
stolen_images,
invalid_price,
insufficient_details,
other,
null
moderation_note
string | null

What moderation wrote to you along with the reason, if anything.

manual_delivery_value
integer<int32> | null

The handover time promised, read together with the unit — 2 and hours.

manual_delivery_unit
enum<string> | null

What the value counts. Both are null on a listing delivered instantly.

Opciones disponibles:
minutes,
hours,
days,
null
price
integer<int64>

US cents.

currency
string

Always USD.

Ejemplo:

"USD"

images
string<uri>[]
delivery_type
enum<string>

instant sells out of the unit pool; manual you hand over yourself.

Opciones disponibles:
instant,
manual