A SaaS application with many users.
An application gives each customer an assistant that remembers and knows their own documents. When someone asks for deletion, it has to be provable.
How it is built.
-
One identifier per account
The application creates an end user with
End usersPOST /v1/end-users, and the identifier is its own account ID. -
Memories and files
Through
/v1/memoriesand/v1/end_users/{uuid}/filesit stores what concerns only this person: up to 100 files per end user and 5 GB per team. -
Its own ceiling per customer
FlowModels has no budget per end user. The application reads usage with
BudgetsGET /v1/usage?group_by=end_userand sets its own limit. -
Erasure with a receipt
On a deletion request, it calls
DELETE /v1/end-users/{uuid}and keeps the result ofGET /v1/end_users/{uuid}/erasureson file: status, timestamps and counts, no content.
curl https://api.flowmodels.one/v1/end-users \
-H "Authorization: Bearer $FLOWMODELS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"external_identifier": "customer-42",
"metadata": { "plan": "pro" }
}'