Data flow
Before integrating, it helps to understand how your data moves through Endear. Records enter from your systems, pass through several stages inside the Endear data platform on GCP, and become available to your applications and the API.
flowchart TB
ingest["1 · Data ingestion<br/>API · CSV · FTP · etc."]:::external
subgraph endear["Endear data platform"]
direction TB
validate["2 · Validation"]
transform["3 · Transformation / normalization"]
persist["4 · Persistence"]
indexing["5 · Indexing"]
retrieve["6 · Retrieval"]
validate --> transform --> persist --> indexing --> retrieve
end
access["7 · Application and API access"]:::external
ingest --> validate
retrieve --> access
classDef external fill:#f6f6f6,stroke:#bbb,stroke-dasharray:4 4,color:#333;
Stages
- Data ingestion — You push records into Endear via the GraphQL API, CSV imports, FTP, or another supported integration.
- Validation — Endear checks required fields, types, and basic referential integrity. See Bulk endpoint guidance.
- Transformation / normalization — Records are mapped into Endear's data model.
- Persistence — Normalized records are stored.
- Indexing — Stored records are indexed so they can be searched, filtered & aggregated.
- Retrieval — Indexed data is served to downstream consumers.
- Application & API access — Your apps, the Endear app, and the API read the processed data.
Updated about 1 hour ago
What’s Next
