The request establishes who is making it and whether that caller can access the operation.
Credentials → token → authorised caller
Skip to contentReminders that fit
A reminder service
A dependable core.
Validate early.
Conventional pieces.
Try the reminder
Open reminders playground
Reminders that fit
into other workflows.
A secure, extensible API for creating and managing reminders from apps, services, and AI assistants.
BUILT TO BE CONNECTED
Authenticated access
Validated requests
AI-ready integration
Reminder API200 OK
POST/api/reminders
{
"title": "Design review",
"dueDate": "tomorrow"
} Reminder created
01 / The idea
A reminder service
designed for extension.
Reminder features become more useful when they can be reached from the tool a person is already using. This API creates a dependable boundary for those integrations.
The implementation combines authenticated access, request validation, structured errors, and a conventional REST surface so clients and AI-assisted workflows can manage reminders predictably.
02 / The API in action
A dependable core.
Ready for integrations.
Explore the current API, its access layer, and an AI-assisted reminder flow.
Create and manage. From anywhere.
A REST interface makes reminder operations available to web apps, services, and other clients.
The API provides the reusable reminder layer; the calling interface can stay focused on its own experience.
Client request → reminder API → stored reminder
API in actionRecorded demo
03 / How it works
Validate early.
Fail clearly.
The request pipeline protects the data boundary before work reaches the controller.
04 / The build
Conventional pieces.
A clear service boundary.
- Application
- .NET · ASP.NET Core
The web API, middleware, identity, and request pipeline.
- Data
- PostgreSQL · Entity Framework Core
Persistence and application data access.
- Protocol
- REST · JWT
A client-friendly contract with authenticated requests.
Keep exploring
Try the reminder
playground.
Try creating a reminder through the interactive playground.