API
Storing API data
What's safe to cache, what you must persist, and what should never leave Pierflow.
Pierflow is the system of record for canonical health data — your job is to store just enough to do your job well.
Always store#
| Field | Why |
|---|---|
| policy_id | Stable reference for every member action |
| member_id | Stable reference for the person |
| plan_id | Render plan info quickly without an extra call |
| webhook event ids | Deduplicate retries |
Safe to cache#
| Field | TTL |
|---|---|
| plan summaries | 1 hour |
| provider listings | 24 hours |
| verifications | 60 seconds |
Never store on the client#
Identity documents (BVN, NIN, biometrics) and clinical PHI must stay server-side. Never embed in mobile bundles or browser local storage.