Problem
The Todoist and Todoist Tasks community apps still use the retired Todoist REST v2 task endpoint and old OAuth URLs. They also expect the legacy bare-array task response, so existing installations can show errors or malformed states now that Todoist API v1 returns paginated objects.
Proposed fix
- Preserve both apps’ names, IDs, encrypted OAuth credentials, configuration fields, and existing feature scope.
- Fetch tasks from
https://api.todoist.com/api/v1/tasks/filter using query and limit=200.
- Parse the current
{results, next_cursor} response; show 200+ in the count app when another page exists.
- Keep the list app to one API page and sort that page by priority.
- Update authorization and token endpoints and include the redirect/grant parameters supplied by Tidbyt OAuth.
- Version cache keys so old REST v2 payloads cannot be reused.
- Correct empty, hidden-empty, unauthenticated, cached, and API-error rendering.
- Validate synthetic zero/one/many/200+/priority/long-text states with Pixlet and do not publish real Todoist content in preview artifacts.
Todoist API reference: https://developer.todoist.com/api/v1/
Problem
The
TodoistandTodoist Taskscommunity apps still use the retired Todoist REST v2 task endpoint and old OAuth URLs. They also expect the legacy bare-array task response, so existing installations can show errors or malformed states now that Todoist API v1 returns paginated objects.Proposed fix
https://api.todoist.com/api/v1/tasks/filterusingqueryandlimit=200.{results, next_cursor}response; show200+in the count app when another page exists.Todoist API reference: https://developer.todoist.com/api/v1/