This document provides an overview of the API resources, which are considered separate entities.
In the Wallapop API, a "user" is a professional seller who connects to the API using their application and credentials.
The item is the core resource of the Wallapop API, representing anything for sale, such as clothing, electronics, or furniture. The API allows users to programmatically publish items.
Each item must be assigned a category. Wallapop has over 800 categories, organized into hierarchies. For instance, "Collectibles & Art" has a sub-category "Antiques."
You cannot assign broader categories directly to items; instead, select the most specific category. This may require analyzing category hierarchies. If you have varied inventory, consider grouping related categories for efficient publishing.
Each category has specific attributes, which can be seen as the "columns" in your data source, like a database or Excel spreadsheet, that describe the items for sale.
When publishing an item, it’s crucial to identify the correct category and the attributes accepted by the API. Each category has unique attributes, with some required and others optional. Attributes may also have constraints, such as a max_length for text types. Including an invalid attribute or not adhering to constraints will result in an API error.
A transaction refers to the process following a buyer's purchase on Wallapop.
Key concepts in the Transactions API include:
- A shipping request occurs when a buyer pays for an item and its delivery fees. Sellers must accept these requests via the API.
- A shipping transaction is created when the seller accepts a shipping request, which triggers the shipment process.
Sellers need to accept shipping requests to initiate item delivery. Client applications can list pending requests or set up webhooks for notifications on delivery requests, which can then be accepted for home pickup or post office drop-off.
A webhook allows your app to receive real-time notifications from Wallapop about specific events, such as items going out of stock or sales being completed.
By subscribing to relevant events, your app can take action automatically when they occur. The webhooks API manages subscriptions to item-related events, and you can create webhooks by sending requests to the POST /webhooks endpoint.
With a foundational understanding of the core API resources, let's explore the steps for effectively publishing items.