This introduction summarizes the entities and operational concepts behind the Recuro workspace so product and engineering teams can align around the same mental model.
Domain model
The API is organized around recurring items, schedules, reminder configurations, delivery events, channels, and authenticated user workspaces.
Concepts
Practical integration use
The most natural integrations focus on syncing recurring records, reading operational state, and connecting channel-aware workflows to external systems.
Use cases
Move from concepts to route-level expectations through the API reference overview.