Skip to content

Changelog

We'll share updates and changes to the Depop Selling API here. This will help you stay informed about new features, improvements, and any breaking changes.

Subscribe to updates

Subscribe to our RSS feed to get notified of changes. It works with any RSS reader, for example, the Slack RSS app.

May 2026

Feature api/v1/pricing Pricing Inspiration

You can now get price predictions and similar sold items through the API!

New endpoint available:

  • POST /api/v1/pricing/inspiration/ - Get pricing inspiration for a product listing

This endpoint provides a predicted price range along with similar sold items to help sellers make informed pricing decisions when listing items.

Note: Pricing inspiration is currently available only for UK and US items. This endpoint does not require OAuth scopes.

To learn more about how pricing inspiration works and its limitations, see the Pricing Inspiration documentation.

April 2026

Improvement api/v1/orders Seller shipping fee in fee breakdown

We've added SHIPPING_FEE to the seller fee breakdown in order responses.

The seller_fee_breakdown array now includes a SHIPPING_FEE entry that represents the cost of shipping labels when the seller pays for shipping (e.g. when using Depop shipping). This fee will be 0.00 when the buyer pays for shipping.

This enhancement provides complete visibility into all seller costs associated with an order, including shipping label expenses that are deducted from the seller's payout.

What's new

  • New fee type: SHIPPING_FEE is now included in the seller_fee_breakdown array for all orders
  • When it applies: The amount will be greater than 0.00 when the seller pays for a Depop shipping label.
  • Buyer-paid shipping: When the buyer pays for shipping, this fee will still appear but with an amount of 0.00

Example

{
  "seller_fee_breakdown": [
    {
      "fee_type": "PAYMENT_FEE",
      "amount": "2.00",
      "currency": "GBP"
    },
    {
      "fee_type": "DEPOP_FEE",
      "amount": "3.00",
      "currency": "GBP"
    },
    {
      "fee_type": "SHIPPING_FEE",
      "amount": "6.75",
      "currency": "GBP"
    }
  ]
}

In this example, the seller paid £6.75 for a Depop shipping label, which is reflected in the fee breakdown.

Improvement webhooks Product slug in like/unlike webhooks

Product like and unlike webhooks now include the slug field in their payload!

The slug field provides the URL-friendly identifier for the product on Depop, making it easier to reference products in your integration without relying solely on product IDs or SKUs.

Webhook event types affected:

  • v1:product.like - Sent when a user likes a product
  • v1:product.unlike - Sent when a user unlikes a product

The slug field is included alongside existing fields: seller_id, product_id, sku (optional), and liker_id.

Feature api/v1/products Boosting

You can now boost and unboost products through the API!

Use the is_boosted field when creating or updating a product to control whether it appears in boosted placements. The field is also included in product responses.

To learn more about how boosting works and its implications for your integration, see the Boosting documentation.

March 2026

Feature api/v1/shop Seller details

You can now retrieve your seller details through the API!

New endpoint available:

  • GET /api/v1/shop/ - Get seller details including your ID, username, and country code

This endpoint requires the shop_read OAuth scope and allows you to retrieve basic information about your Depop shop.

Feature api/v1/products Slug-based product endpoints

You can now manage products using their Depop slug in addition to SKU and product ID!

New endpoints available:

  • GET /api/v1/products/by-slug/:slug/ - Get product by slug
  • PUT /api/v1/products/by-slug/:slug/ - Update product by slug
  • PATCH /api/v1/products/by-slug/:slug/ - Partially update product by slug
  • DELETE /api/v1/products/by-slug/:slug/ - Delete product by slug
  • POST /api/v1/products/by-slug/:slug/mark-as-sold/ - Mark product as sold by slug
  • POST /api/v1/products/by-slug/:slug/offer/ - Submit an offer by slug

The slug field is now included in all create and update responses, including:

  • PUT /api/v1/products/by-sku/:sku/
  • PUT /api/v1/products/by-product-id/:productId/
  • PUT /api/v1/products/by-slug/:slug/
  • POST /api/v1/products/

February 2026

Feature api/v1/products Manual offer submission

You can now manually submit offers to specific buyers through the API!

New endpoints available:

  • POST /api/v1/products/by-product-id/:productId/offer/ - Submit an offer by product ID
  • POST /api/v1/products/by-sku/:sku/offer/ - Submit an offer by SKU

These endpoints allow you to send targeted offers to individual buyers, giving you more control over the negotiation process.

Head over to the Managing Offers documentation to learn more.

Feature api/v1/products Discounts

We now support setting discounts for listings through the API!

When you provide a discount_price, the original price is still shown to the buyers with a strikethrough (for example, $20 $15).

January 2026

Feature api/v1/products Depop Managed Shipping

We now support Depop Managed Shipping for listings through the API!

When creating or updating a product, you can now specify depop_shipping instead of national_shipping_cost.

This allows Depop to handle shipping logistics, including calculating shipping costs based on the selected provider and parcel size.

Head over to the Shipping documentation to learn more about Depop Managed Shipping.

December 2025

Feature api/v1/shop/seller-addresses Seller address management

We now support retrieving seller shop info using the API!

New endpoints available:

  • GET /api/v1/shop/seller-addresses/ - List all seller addresses
  • GET /api/v1/shop/seller-addresses/:addressId/shipping-providers/ - List shipping providers and parcel sizes for a specific seller address

These endpoints allow you to retrieve available shipping options with their parcel sizes based on the seller's address.

November 2025

Feature api/v1/products Product ID endpoints

We now support managing products by product ID in addition to SKU-based endpoints.

New endpoints available:

  • POST /api/v1/products/ - Create a new product (returns product ID)
  • GET /api/v1/products/by-product-id/:productId/ - Get product by ID
  • PUT /api/v1/products/by-product-id/:productId/ - Update product by ID
  • PATCH /api/v1/products/by-product-id/:productId/ - Partially update product by ID
  • DELETE /api/v1/products/by-product-id/:productId/ - Delete product by ID
  • POST /api/v1/products/by-product-id/:productId/mark-as-sold/ - Mark as sold by ID
  • POST /api/v1/products/by-product-id/:productId/purchase/ - Simulate purchase by ID (staging only)

These endpoints support products without SKU fields, providing more flexibility for partners who prefer to manage inventory using Depop's product IDs rather than external SKUs.

Important changes:

  • The sku field is now optional in product responses. Existing users who exclusively use SKU-based workflows will always have this field populated.
  • Legacy product endpoints without the /by-sku/ prefix are now deprecated. Please update your integration to use the /by-sku/ endpoints:
    • /api/v1/products/:sku/ → /api/v1/products/by-sku/:sku/
    • /api/v1/products/:sku/mark-as-sold/ → /api/v1/products/by-sku/:sku/mark-as-sold/
  • The legacy endpoints will continue to work for now, but we recommend migrating to the new URLs to ensure compatibility with future updates.

October 2025

Improvement api/v1/products WebP support for images

We now support WebP images for product listings in addition to PNG and JPEG.

Note: Transparency is not supported as we are converting WebP images to JPEG internally. A white background will be applied to the image.

September 2025

Improvement api/v1/orders Enhanced refund details

We now provide detailed refund breakdowns in order responses.

The refund_summary object now includes a breakdown field that shows how refund amounts are distributed between buyer and seller for different components (items, shipping, fees).

This enhancement provides greater transparency into refund calculations and helps partners understand the full refund structure.

August 2025

Feature api/v1/products Automatic Brand matching

We now handle brand matching automatically using brand_name.

Action required: Please update your integration to use brand_name instead of brand. The brand_name field is now mandatory for all new partner integrations.

July 2025

Feature api/v1/products Auto-negotiate offers

Auto-negotiate offers is now available!

This feature allows you to automatically respond to offers from your buyers. Together with Auto-send, this can help you fully automate the handling of offers.

To learn more how you can use this feature, please refer to the Managing offers documentation.

Improvement api/v1/products PNG support for images

We now support PNG images for product listings in addition to JPEG.

Note: Transparency is not supported as we are converting PNG images to JPEG internally. A white background will be applied to the image.

June 2025

Feature api/v1/products Refunds

You can now process full or partial refunds for your orders using the API directly.

To learn more about how to use this feature, please refer to the Refunds documentation.

Improvement api/v1/products Multi-quantity support

You can now create listings with a quantity greater than 1.

Important: that you should only call Mark as Sold when it's completely sold out and use the PUT or PATCH endpoint to update the quantity.

Feature Public API documentation

We have invested in improving our API documentation to make it more comprehensive and self-serving.

If you have any feedback or suggestions, please reach out to us at [email protected].

May 2025

Feature api/v1/products Auto-send offers

Auto-send offers is now available!

This feature allows you to automatically engage with your buyers that have liked or bagged your product by sending them an offer.

Head on to our API Reference documentation to learn more about the auto_send_offer_price field.

Improvement api/v1/products Restocking

You can now restock your listings that were previously sold out or deleted.

To learn more about how to restock your listings, please refer to the Restocking documentation.