Developers › Docs
FLUF developer docs
Build marketplace workflows with the FLUF API, webhooks and MCP. Read inventory and orders, create drafts and connect your own tools. Check the supported actions and access requirements before building.
Start here
Getting started
Create a token and make your first call in two minutes.
Guide
Webhooks
A signed POST to your server the moment an item sells, anywhere.
Guide
MCP server
Let Claude, Cursor or any MCP client work your account.
Reference
REST API
Every endpoint, with request, response and errors.
API reference
/accountsList accounts/productsCreate a productPOST/products/importImport productsGET/products/import/{id}Get import progress/itemsPublish or repricePATCH/items/{vid}Update a productGET/itemsList itemsGET/items/{vid}Get an itemDELETE/itemsTake listings downPOST/items/{vid}/mark-soldMark as soldDELETE/items/{vid}Delete a product/crosslisting-tasksCrosslisting tasks/draftsList draftsPOST/drafts/{id}/approveApprove a draftGuides
What's supported
What the API can and can’t do, which plan includes it, browser-run marketplaces, testing, and building for other sellers.
Webhooks
Register an endpoint, verify a signature, and handle retries correctly.
Webhook events
Every webhook event we send, what it carries, and when it fires.
MCP server
Let an AI assistant work a FLUF account directly.
UCP for AI shopping agents
FLUF speaks the Universal Commerce Protocol: agents can discover, search and look up secondhand inventory.
Start with the workflow you need
For a sales spreadsheet, team alerts or a packing queue, start with the n8n workflow templates or Zapier recipes. They include a concrete example and a setup guide for each workflow.
Building a custom integration? Start with the getting-started guide, then check supported operations and access. Use the endpoint reference for request fields and the webhooks guide for event handling.
For marketplace setup, inventory sync or troubleshooting without code, visit FLUF docs and seller guides.
Machine-readable
Two OpenAPI documents, both public — you don't need a token to read them. Point a client generator at either.
openapi.yaml— the endpoints you callevents.yaml— the events we sendGET /events— every event with a sample payload, generated from the running code
Something missing? Email [email protected] — we prioritise by what people actually ask for.
