One OAuth client per supplier, for every stock movement
Suppliers send traceability events with standard client credentials. Each one can be revoked on its own, and no supplier can post as another.
Illustrative scenario based on patterns we see across teams building on Faable.

The team
A mid-sized European retailer with stores and an online shop. Its platform team receives EPCIS events from suppliers and logistics partners whenever a pallet ships, reaches the warehouse or lands in a store.
The challenge
Dozens of suppliers post to the same endpoint, and the industry expects OAuth 2.0 client credentials, not an API key shared by email. When a supplier leaves or leaks a credential, only that supplier should lose access. And no supplier should ever post events as another, because inventory and claims depend on knowing who said what.
How they built it
- 1
One API for event capture
The receiver accepts only tokens issued for the events API, which has a single write permission.
- 2
One machine client per supplier
Every supplier gets its own client_credentials client. Those with their own infrastructure authenticate with a private key instead of a secret, and each client can be revoked on its own.
- 3
The sender comes from the token
A client-credentials Action lets only registered suppliers get a token and stamps the supplier's id into it. The receiver reads who sent each event from the signed token, never from the payload.
- 4
Roles for store teams
Store managers sign in to read events, and the inventory team can also correct them. Each role decides what that person's token carries.
- 5
A small receiver on Faable Deploy
The receiver is a FastAPI app that answers 202 on capture, as EPCIS 2.0 expects, and stores events in a managed database.
The result
Standard OAuth for every supplier, with revocation one supplier at a time. Every event is attributable to its sender, every token issued is in the logs, and the whole pipeline is hosted in the EU.

