Seller API — auctions, lots, inventory, settlements

Seller integrations use Sanctum tokens with the seller ability and optional X-Team-Id header for multi-team accounts. All responses use the standard success envelope.

Auctions

1. GET /api/v1/seller/auctions — list your auctions (filter status, search).
2. POST /api/v1/seller/auctions — create draft auction (title, category_id, start_time, end_time, …).
3. GET /api/v1/seller/auctions/{id} — detail.
4. PATCH /api/v1/seller/auctions/{id} — update fields.

Lots

1. GET /api/v1/seller/lots — list lots you own.
2. POST /api/v1/seller/lots — create lot (auction_id, title, starting_bid, …).
3. GET /api/v1/seller/lots/{id} — detail with images.
4. PATCH /api/v1/seller/lots/{id} — update lot fields.

Inventory

1. GET /api/v1/inventory — paginated warehouse items.
2. POST /api/v1/inventory — create inventory item.
3. PATCH /api/v1/inventory/{id} — update item.
4. GET /api/v1/inventory/aging-summary — bucket counts by days in stock.
5. POST /api/v1/inventory/convert-to-lots — promote items to lots (auction_id, item ids).

Settlements & media

1. GET /api/v1/settlements — settlement statements for sold lots.
2. GET /api/v1/settlements/{id} — single settlement with lot/auction embed.
3. POST /api/v1/media — multipart upload (file, model_type lot|auction|inventory_item, model_id, collection).

Reference

• OpenAPI JSON
• Seller endpoints (HTML)
• API tokens

Last updated: 2026-07-13