Update a project
PATCH/api/projects/:id
Required permissions:
- pipeline.edit: to update a project where the user is PM or Account
- pipeline.edit_other: to update a project where the user is not PM nor Account
- pipeline.job_order: to update a project job order
Here the dedicated support page.
Project metadata
You can set project metadata values using the
dynamic field like metadata_13
where 13
is the ID of the project metadata you want to set.
You can get all the available project metadata using the related endpoint.
Only project metadata with a value will appear in the response.
As of today, this endpoint does not support the following functionalities:
- Archiving or unarchiving a project
- Manage timesheet whitelist for a project
- Setting opportunity stage
- Setting project risk
- Setting won/lost feedback
Are you interested in any of these? Let us know!
Request
Path Parameters
The ID of the project to update
Header Parameters
The company you want to interact with
The API version you want to use
- application/json
Body
Possible values: <= 500 characters
Project name
ID of the client of this project
ID of the client contact for this project
Project purchase order
ID of the person designed to manage this project
ID of the person designed as account for this project
ID of the job order category to associate to this project
ID of the project type to associate to this project
Possible values: <= 150 characters
Project job order
The value of the project in K
Possible values: <= 100
Duration of the project in months
Estimate of the external costs as percentage of the project value
Project start month. This follows the YYYY-MM-DD format
Possible values: >= 1
The probability of the project
The date the project is supposed to end
The date the project has been signed
ID of the business unit to which this project belongs
Responses
- 200
- 400
- 401
Returns the updated project.
- application/json
- Schema
- Example (from schema)
Schema
Possible values: >= 1
The value of the project in K
Possible values: <= 100
The probability of the project
The first day of month where the project started
Possible values: >= 1
Duration of the project in months
The date the project was archived
The date the project is supposed to end
The date the project has been signed
Possible values: >= 1
ID of the job order category
Possible values: >= 1
ID of the project type
Possible values: >= 1
ID of the client
Possible values: >= 1
ID of the person who is the project manager
Possible values: >= 1
ID of the person who is the account
Possible values: >= 1
ID of the client contact
Possible values: >= 1
ID of the reason why the project is won or lost
Possible values: >= 1
ID of the business unit
Possible values: >= 1
ID of the billing group the project is in
{
"id": 1,
"created_at": "2025-02-13T09:26:18.858Z",
"updated_at": "2025-02-13T09:26:18.858Z",
"name": "First project",
"job_order": "jo_001",
"purchase_order": "po_001",
"value": "1.5",
"probability": "50",
"date_start": "2024-01-01",
"duration": "4",
"is_archived": true,
"archived_on": "2024-01-01",
"due_date": "2024-01-01",
"signed_on": "2024-01-01",
"job_order_category_id": 1,
"project_type_id": 1,
"client_id": 1,
"pm_id": 1,
"account_id": 1,
"client_contact_id": 1,
"reason_why_id": 1,
"business_unit_id": 1,
"billing_group_id": 1
}
Validation failed
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
Error unique key
Human-readable message describing the error
failures
object[]
List of validation errors
Name of the field causing the error
Human-readable description of the error
{
"key": "invalid_data",
"message": "You provided invalid data. Check 'failures' for details.",
"failures": [
{
"field": "string",
"message": "string"
}
]
}
Unauthorized
- application/json
- Schema
- Example (from schema)
Schema
Error unique key
Human-readable message describing the error
{
"key": "string",
"message": "string"
}