folk API
GET /v1/interactions/upcoming endpoint removal
Stops workingSubscribe to folk APIShare
On March 29, 2027, the folk API will remove the GET /v1/interactions/upcoming endpoint. Requests sent to this route after that date will fail. Calls to the endpoint currently return deprecation and sunset headers ahead of the shutdown.
Calls it hits
GET /v1/interactions/upcoming
What to use instead of these calls
Update requests to call GET /v1/interactions with timeframe=upcoming instead.
In folk API's words
List past interactions and List upcoming interactions are deprecated, now return Deprecation / Sunset headers and will be removed on March 29, 2027.
Facts
- API
- folk API
api.folk.app - Kind
- Endpoint removal
- Announced
- September 29, 2026
- Takes effect
- March 29, 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 GET /v1/interactions/upcoming on folk API stop working on March 29, 2027.
What happens to calls after March 29, 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 -
/v1/reminders/{id}Endpoint removal Stops workingin 99 days -
GET /v1/interactions/pastEndpoint 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 March 29, 2027.