The questions customers ask, as endpoints.
“Where is my order? Was it delivered? What was received? Where's the invoice?” The Customer Order API answers each of these programmatically, against the same order trail FilFlo's operations workspace runs on.
Order status
Read the current status of an order as it moves through approval, fulfillment and delivery — the same order trail FilFlo's own workspace runs on.
Delivery confirmation
Confirm delivery against an order programmatically, so the order trail reflects what actually arrived without a manual update.
GRN submission
Submit goods-receipt data against an order. GRNs recorded through the API feed the same invoice-vs-GRN variance workflow the rest of FilFlo uses.
Invoice download
Download the invoice document for an order — useful for customer portals, shared drives and downstream systems that need the actual PDF.
Invoice & credit-note reports
List invoice and credit-note reports, and export invoice reports as header- or line-level CSV — so finance-side systems can pull document listings on their own schedule.
Scoped keys, predictable limits.
Every request authenticates with an API key sent in the X-API-Key header. Keys are scoped — by workspace, by customer, and by endpoint — so an integration gets exactly the access it needs and nothing else.
X-API-Key: <your-scoped-key>Workspace-wide or customer-scoped
A key can be issued for the whole workspace, or scoped down to a single customer — so a buyer or partner only ever sees their own orders.
Per-endpoint scopes
Every endpoint declares the scopes it requires and each request is checked against the key — keys can be restricted to exactly the endpoints an integration needs.
Workspace isolation
Keys are bound to one workspace. Data from other workspaces is unreachable by design, not by convention.
100 requests/minute per key
Each API key gets its own budget of 100 requests per minute, so one integration can't starve another.
Standard rate-limit headers
Responses carry standard rate-limit headers, so clients can read their remaining budget and back off cleanly instead of guessing.
Webhooks that work in both directions.
Order Hooks is FilFlo's bidirectional webhook system for order lifecycle events: events flow out of FilFlo to your systems as an order progresses, and events from your systems flow back into the same order trail. It's organised in three layers, so every subscription is explicit rather than hard-wired.
Hooks
The order lifecycle events that can be subscribed to — the points in an order's life where something worth reacting to happens.
Bindings
The wiring: a binding connects a hook to the handler that should run when the event fires, so subscriptions are explicit and auditable.
Plugins
The handlers themselves — the units that process or deliver an event once a binding routes it to them.
The docs live in the open.
fillfow/filflo-api-documentation
Endpoint references for the Customer Order API and Order Hooks, authentication and scope details, and rate-limit behaviour — published as a public GitHub repository so you can read it before you ever talk to us.
Building against the order trail?
Tell us what you're integrating — a customer portal, a partner system, an internal dashboard — and we'll walk you through the endpoints, scopes and hooks that fit, then issue keys for your workspace.