Developers
Connect FLUF to whatever you already use
Your spreadsheet, your admin tool, your accountant's system — or an AI assistant. Know the second something sells, anywhere you sell it, without writing a single marketplace integration.
Create an API token Read the docsWebhooks
A signed POST to your server the moment an item sells on any connected marketplace.
REST API
Read your inventory and orders, and list items to marketplaces, over plain HTTPS.
MCP server
Let Claude, Cursor or any MCP client run your shop in plain language.
One integration instead of fifteen
Every marketplace has its own idea of what a product is — different categories, size systems, brands, condition values and photo rules. Several have no public API at all. FLUF already speaks all of them, so you integrate once and reach every channel your account is connected to.
You never touch marketplace credentials, and you don't redo the work every time a channel changes something.
Know the second something sells
Point FLUF at a URL and it'll POST there as sales come in:
curl -X POST "https://fluf.io/wp-json/fc/api/v1/webhooks" \
-H "Authorization: Bearer fluf_pat_your_token" \
-H "Content-Type: application/json" \
-d '{"url":"https://yourapp.example.com/hooks/fluf","events":["new_sale"]}'Every sale arrives like this:
{
"event": "new_sale",
"sku": "T-001",
"channel": "depop",
"price": 45.00,
"currency": "GBP",
"sold_at": "2026-07-28T14:03:11+00:00",
"title": "Vintage Levi's 501 jeans",
"order_id": "abc-123-def"
}
sku is your reference code, read from the item in FLUF — so it
already matches whatever your own system calls it. No lookup table, no guessing
which listing sold.
Deliveries are signed so you can prove they came from us, retried if your server is down, and every attempt is logged — so you can always check whether one fired. Full webhook documentation →
What you can listen for
| Event | Fires when |
|---|---|
new_sale | An item sold on any connected marketplace |
new_listing | A product was created in FLUF |
listing_crosslisted | A product went live on a marketplace |
crosslisting_error | A listing attempt failed |
listing_sold_out | A product is no longer live anywhere |
oos_alert | Stock hit zero |
crosslisting_job_completed | A bulk listing run finished |
Let an AI assistant run your shop
FLUF ships a Model Context Protocol server, so any MCP-compatible assistant can work your account directly. Add it to Claude, Cursor, Cline or anything else that speaks MCP:
{
"mcpServers": {
"fluf": {
"command": "npx",
"args": ["-y", "@fluf/mcp"],
"env": { "FLUF_API_TOKEN": "fluf_pat_your_token" }
}
}
}Then just ask it:
- “What's in stock that isn't on eBay yet? List the ten cheapest.”
- “What sold last week, and on which channel?”
Source is open on GitHub.
Get started in two minutes
- Open Settings → Developer in FLUF Connect.
- Create an API token. It's shown once and starts with
fluf_pat_. - Send it as
Authorization: Bearer <token>.
Included with any paid FLUF plan — there's no separate developer tier.
Need something we haven't built yet? Email [email protected] — we prioritise by what people actually ask for.