Evaluate "due" on rtm.tasks.add (API V2)
TL;DR, allow this on API v2:
?method=rtm.tasks.add&date=2025-07-11
...or this I guess:
?method=rtm.tasks.add&date=2025-07-11T10%3A30%3A00%2B00%3A00
-----
Gory Details:
I've discovered that the API's rtm.tasks.add method ignores the "due" parameter, e.g.
{
due: '2025-01-01'
}
And as a result tasks were being added without any due date (which, in my utilzation of RTM, makes the tasks effectively hidden from view).
As a workaround, I'm setting the tasks to be parsed using natural language to set a due date:
{
parse: 1,
name: task + ' today'
}
Because the yet-to-be-created tasks don't have a "task_id" I don't see a way to use the rtm.tasks.setDueDate method. Is there another way I'm missing with either tasks.setDueDate or tasks.add?
?method=rtm.tasks.add&date=2025-07-11
...or this I guess:
?method=rtm.tasks.add&date=2025-07-11T10%3A30%3A00%2B00%3A00
-----
Gory Details:
I've discovered that the API's rtm.tasks.add method ignores the "due" parameter, e.g.
{
due: '2025-01-01'
}
And as a result tasks were being added without any due date (which, in my utilzation of RTM, makes the tasks effectively hidden from view).
As a workaround, I'm setting the tasks to be parsed using natural language to set a due date:
{
parse: 1,
name: task + ' today'
}
Because the yet-to-be-created tasks don't have a "task_id" I don't see a way to use the rtm.tasks.setDueDate method. Is there another way I'm missing with either tasks.setDueDate or tasks.add?
Log in
to post a reply.