folk API
/v1/reminders/{id} endpoint removal
Stops workingSubscribe to folk APIShare
On February 13, 2027, the /v1/reminders/{id} endpoint will be removed and calls to it will fail. The folk API announced this change on August 13, 2026, noting that reminders endpoints now return Deprecation and Sunset headers ahead of their permanent shutdown.
Calls it hits
/v1/reminders/{id}
What to use instead of these calls
Use the Tasks endpoints instead (GET, PATCH and DELETE /v1/tasks/{taskId}), following folk's reminders-to-tasks migration guide.
In folk API's words
Reminders endpoints now return Deprecation / Sunset headers and will be removed on February 13, 2027.
Facts
- API
- folk API
api.folk.app - Kind
- Endpoint removal
- Announced
- August 13, 2026
- Takes effect
- February 13, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against folk API's own pages
Questions
When does this change take effect?
Calls to /v1/reminders/{id} on folk API stop working on February 13, 2027.
What happens to calls after February 13, 2027?
They fail from that day.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from folk API 3
-
/v1/remindersEndpoint removal Stops workingin 99 days -
GET /v1/interactions/pastEndpoint removal Stops workingin 143 days -
GET /v1/interactions/upcomingEndpoint removal Stops workingin 143 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before February 13, 2027.