Get a project
One project (404 when it belongs to another org).
View as MarkdownAuthorization
bearer In: header
Path Parameters
uuidResponse Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08"{ "project": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "teamId": "a4ede8ba-7c0a-4485-8763-cbd9b282fbec", "name": "string", "description": "string", "status": "planned", "leadId": "3c6e2b8e-0e8f-48db-8791-27271df10113", "targetDate": "2019-08-24", "created": "2019-08-24T14:15:22Z", "modified": "2019-08-24T14:15:22Z" }}Create a project
Status defaults to "planned". leadId must reference a member of the caller's org (else 400 "invalid leadId"); an empty-string leadId is treated as null. targetDate accepts YYYY-MM-DD (or RFC3339, truncated to the day). The team must belong to the caller's org (else 404). `name` is stored trimmed and must be unique within the team, compared case-insensitively — a name already in use is a 409.
Update a project
Partial update. Setting leadId to "" clears the lead; a non-empty leadId outside the org's members is 400 "invalid leadId". A `name` that another project in the same team already uses is a 409; a blank one is a 400. Re-sending the project's own name is always allowed.