<aside>
ℹ This page describes the suggested and currently most effective way to create listings/offers on refurbed. Listing requests created this way will be treated with higher priority than via email.
</aside>
All services and operations concerning the offers must be called with CatalogService or OfferService in the URL followed by the command/operation.
E.g.: https://api.refurbed.com/refb.merchant.v1.OfferService/BatchCreateOffers
or
https://api.refurbed.com/refb.merchant.v1.CatalogService/GetCatalogTemplates
All calls must be done using POST method.
Our Next Gen Listing workflow allows you to send us your to be listed product and offer data in one action in contrary to our previous workflow, where listing and offer creation were two separate steps, and only offer creation was available in the Seller API. This new workflow is a more commonly used template based workflow as it is used by many platforms and provides more convenience and scaleability to you.
GetCatalogTemplates)<aside>
⚠ Currently available category templates: Laptops, Desktops, Tablets, Audio, E-Bikes, Smartwatches, Accessories, Cameras, Consoles, Monitors, Printers, Smartphones and TVs. More will be added soon.
</aside>
This method exposes our category templates. Provide category_type (ELECTRONICS, SPORTS or KIDS) and lang_code (DE, EN) in the request payload to retrieve all category templates for a certain category type at once. You can also specify a specific category_id to only receive the template of a certain category. On the root of the response object you will find category_id, category_name, child_templates and version. While category_id and category_name specify what their names imply child_templates will expose if there are more specific templates available for sub categories; version is incremented every time we do an update on a template.
The constraints section holds the template definitions as a list of objects, whereas each product attribute is represented by one object:
| field name | description |
|---|---|
| attribute_key | This value has to be used as key when sending us a listing request, e.g.: screen_size or operating_system. |
| attribute_name | Human-readable name of the attribute key e.g.: Screen Size or Operating System, The localization of this name depends on the chosen lang_code in the request (DE, EN). |
| presence | Indicates whether the attribute is either REQUIRED or OPTIONAL in the listing request. |
| known_values | For some attributes we will expose commonly used values in our product data to provide guidance on expected values sent in a listing request e.g.: yes/no In most cases these are example values and not an exhaustive list, more values might be possible. |
| value_type | Specifies the expected value type e.g.: INTEGER, DECIMAL or STRING |
| description | Here we provide additional information e.g. examples or formatting hints. Localization of this text depends on chosen lang_code sent in the request. |
| unit | This field is only visible for numeric attributes where we expose the unit to be used in the listing request, e.g.: GB |
BatchCreateOffers)