Discover operations
Read data
All operation calls usePOST /v1/vinted/mobile/{operation} with a JSON body:
operation, market, and the upstream JSON in data.
Each successful read costs 1 credit. Failed requests are free. An empty
collection can be a valid result; the operation description identifies inputs
that returned empty or limited data during validation.
Sold comparables are a sample of similar sold listings, not an exhaustive sales
history. Their prices are not guaranteed final negotiated settlement prices.
The
price-suggestions operation returns Vinted’s suggested price and range.CLI and MCP
CLI version 0.14.0 or later:vinted_mobile_operations to discover inputs, then
vinted_mobile_read with operation, market, and parameters. Existing Vinted
MCP tools remain available.
Search and field changes
/v1/vinted/searchalso acceptssize_ids,material_ids,time, andsearch_session_id. Reuse the returned paginationtimeand your search session across pages. Live results can overlap; deduplicate by item ID.marketselects the locale and catalog region. It does not limit listings to sellers physically located in that country. Use the existingseller_countryfilter on/searchwhen you need that restriction. Core reads use the requested country so prices and region-specific wardrobes match that market.- Search URLs are absolute.
display_titleanddisplay_subtitleretain Vinted’s presentation labels.brand_titleis null when the response does not provide a reliable brand field; a display label can include a model name. - Item details return descriptions, brand/category/condition IDs and photos. Unavailable fields remain null. A size-guide or condition FAQ link ID is not an item attribute ID.
- These operations read public data. They do not perform purchases, payments, messages, account changes or listing publication.
Operation catalog
The tables below list every operation. Use discovery for full parameter types, optional fields and runnable examples. Parameters belong insideparameters,
including identifiers used to select an item, seller or category.
Discovery
Listing age on catalog search
Vinted sends no upload time on search results.catalog-search adds an estimate to every item, at the same 1 credit:
Vinted’s item IDs are one global sequence across markets, so an ID can be placed between listings whose times we know. Those reference times come from the photo stamps of item-details responses, including a listing we read every few minutes to keep the most recent IDs covered. The error depends on how close those references are:
About 1% of listings are off by more than a day even with close references. These are drafts published later or relisted items, whose ID is older than the moment they went live. An item older than every reference comes back
null. An item newer than every reference is placed between the newest reference and the time of the response.
Each response also carries uploaded_at_reference, which tells you how far back the estimates reach:
null if the reference table is briefly unavailable, in which case every estimate is null too and the search itself still succeeds.
Items
item-details returns Vinted’s payload unchanged except for one field we add: item.uploaded_at, an ISO 8601 UTC timestamp taken from the earliest photo upload. It is approximate in both directions. A seller who replaces a photo after listing moves it later, and a photo uploaded before the listing is published can predate it by about 30 minutes. Related items carry no upload time.
related-items takes content_source similar_items or other_user_items. To get the next page, send the previous response’s next_page_token. When it is null there are no more pages.
Sellers
Reference
Shipping
Help
Configuration
Pricing
Python and Node SDKs
Use SDK version 0.46.0 or newer. Python takes apayload keyword; Node takes the JSON body as its second argument.

