> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/deployment-and-it-ops/integrations-and-api-access/integrations/oauth-for-direct-api-access/project-suite/create-task-api.md).

# Create Task API

Create tasks and assign project members.

Create a task under a project. Set assignees directly on the task.

{% hint style="warning" %}
This route maps to an internal API. Confirm its external gateway path, OAuth scopes, and rate limits before client use.
{% endhint %}

### Endpoint

```http
POST https://api.in.we360.ai/api/v1/tasks/
```

### Request body

```json
{
  "project_id": "a1b2c3d4-1111-2222-3333-444455556666",
  "type": "TASK",
  "summary": "Draft deposition outline",
  "description": "Prepare outline for the 4821 deposition.",
  "status": "TODO",
  "assignee_ids": ["f9c8f8f8-1111-2222-3333-444455556666"],
  "reviewer_id": "aa11bb22-3333-4444-5555-666677778888",
  "parent_id": null,
  "start_date": "2026-04-02",
  "due_date": "2026-04-05",
  "estimate": "04:00:00",
  "external_ref": "CASE-4821-T1"
}
```

| Parameter                | Required | Description                                           |
| ------------------------ | -------- | ----------------------------------------------------- |
| `project_id`             | Yes      | Parent project UUID.                                  |
| `summary`                | Yes      | Task title.                                           |
| `type`                   | No       | `EPIC`, `TASK`, or `BUG`. Defaults to `TASK`.         |
| `status`                 | No       | `TODO`, `IN_PROGRESS`, or `DONE`. Defaults to `TODO`. |
| `description`            | No       | Detailed task description.                            |
| `assignee_ids`           | No       | User UUIDs assigned to the task.                      |
| `reviewer_id`            | No       | Reviewer UUID.                                        |
| `parent_id`              | No       | Parent task UUID for child tasks.                     |
| `start_date`, `due_date` | No       | ISO scheduling dates.                                 |
| `estimate`               | No       | Time estimate in `HH:MM:SS`.                          |
| `external_ref`           | No       | External task ID for correlation.                     |

Assignees must already be project members. Add them first if needed.

### Response

Returns `201 Created`.

```json
{
  "id": "c7d8e9f0-aaaa-bbbb-cccc-ddddeeeeffff",
  "task_key": "ACME-142",
  "project_id": "a1b2c3d4-1111-2222-3333-444455556666",
  "type": "TASK",
  "summary": "Draft deposition outline",
  "status": "TODO",
  "assignee_ids": ["f9c8f8f8-1111-2222-3333-444455556666"]
}
```

### Example

```bash
curl -X POST "https://api.in.we360.ai/api/v1/tasks/" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer ${access_token}" \
  -d '{"project_id":"a1b2c3d4-1111-2222-3333-444455556666","summary":"Draft deposition outline","type":"TASK","assignee_ids":["f9c8f8f8-1111-2222-3333-444455556666"]}'
```

Update assignees with `PUT /api/v1/tasks/{id}` and an updated `assignee_ids` array.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.we360.ai/deployment-and-it-ops/integrations-and-api-access/integrations/oauth-for-direct-api-access/project-suite/create-task-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
