Resources

Reference the Recuro API as an operational system, not just a list of endpoints.

This page highlights the families of routes and contract expectations that matter most when integrating recurring item workflows into a broader toolchain.

Core route families

The current application surface revolves around auth, items, schedules, dashboard overviews, reminders, and channel-management workflows.

Routes

  • Auth routes
  • Item and schedule CRUD
  • Dashboard overview and reminder operations

Reference expectations

A good Recuro API reference should make it easy to understand request shape, ownership constraints, delivery-state semantics, and response contracts without guesswork.

Contracts

  • User-scoped resources
  • Reminder-event semantics
  • Operationally useful response payloads

Need implementation support around the API surface?

Use the support route when you need environment-specific clarification or routing guidance for the current product surface.