PUT Update proposal timeline
Update dates under /api/v1/proposal/timeline. Send either or both dates in strict YYYY-MM-DD format. See the response tabs for validation failures and the empty-request response. Proposals converted to projects must be updated through the Project API.
Update proposal dates under /api/v1/proposal/timeline. Send either or both dates as
YYYY-MM-DD. Invalid dates or other date formats return HTTP 400.
The resulting start date must be on or before the finish date; rejected
timeline/resource changes return HTTP 422 without applying the change.
When both dates are omitted, null, or empty, HTTP 204 has no body.
Successful updates return HTTP 200 with status: 201 in the JSON body.
Proposals already converted to projects return HTTP 400; use the
Project API to update those records.
/proposal/timelineAuthorization
Use the standard /api/v1 headers for this request.
Send the target project_token and any timeline changes inside the JSON body.
API Credentials (save your keys here to make the request examples copy-ready)Hidden by default
Save your domain and request headers once, then reuse them across the current docs session.
Session storage clears when this tab closes. Local storage stays available the next time you open the docs in this browser.
Saved values are used in request examples and code snippets on API pages, including the request domain.
Request Body
application/json
Top-level request body type: object. Send JSON fields shown below.
Optional date in `YYYY-MM-DD` format. Null, empty, or whitespace-only means absent, not a request to clear the stored date.
Optional date in `YYYY-MM-DD` format. Null, empty, or whitespace-only means absent, not a request to clear the stored date.
Response Body
application/jsonSuccessful response confirming updated proposal dates.
{
"status": 201,
"message": "Dates updated 2026-06-01 - 2026-12-15"
}Both dates are omitted, null, or empty. No response body.
No response body.
application/jsonInvalid date or non-ISO date format. A converted proposal cannot be changed through this endpoint.
{
"status": 400,
"message": [
"start_date is not a valid date"
]
}application/jsonMissing or invalid integration authentication headers.
{
"errors": [
"Not Authenticated"
]
}application/jsonTimeline or resource update rejected. The change is not applied.
{
"status": 422,
"message": [
"start_date must be on or before end_date"
]
}