Managing project schedules and turnaround times just got much easier—and far more automated.
We’ve updated our Create Task API (POST /tasks) to support setting specific time to due date.
Why this makes your life easier
Whether you are triggering localization tasks from a CI/CD build, an internal CMS, or a custom script, setting relative timeframes gives you automated turnaround management out of the box:
-
Granular control: Set different timeframes for each specific step in the workflow (like
TRANSLATION,REVIEW, orPROOFREAD). -
Smarter SLA tracking: Give your linguists and vendors immediate, predictable deadlines the instant a task goes live.
How it works
When building your request payload for the POST /tasks endpoint, you can now pass time_to_due_dates inside the task attributes object.
Here is an example showing how to set relative due times for translation, review, and proofreading steps:
{
"data": {
"type": "tasks",
"attributes": {
"name": "Transifex task",
"task_type": "TRANSLATION",
"language_codes": [
"l:en",
"l:fr"
],
"resource_string_ids": [
"o:<org_slug>:p:<proj_slug>:r:<res_slug>:s:<string_hash1>",
"o:<org_slug>:p:<proj_slug>:r:<res_slug>:s:<string_hash2>"
],
"assignee_selection_method": "SKIP",
"description": "Translate all resource strings",
"time_to_due_dates": {
"TRANSLATION": "2025-01-01T14:30:00",
"REVIEW": "2025-01-02T14:30:00",
"PROOFREAD": "2025-01-03T14:30:00"
},
"exclusive_editing": true,
"priority": "NORMAL"
},
"relationships": {
"project": {
"data": {
"type": "projects",
"id": "o:organization_slug:p:project_slug"
}
}
}
}
}
IMPORTANT: Timezone Behavior
Time is expected in UTC!