canonical: https://jentic.com/apis/worksection.com/worksection

# Worksection API

Project management and task tracking API. Manage projects, tasks, comments, users, and team schedules. The API exposes 34 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get all tasks, get project tasks. Covers 34 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for productivity only.

## Capabilities

- Get all tasks
- Create task
- Update task
- Complete task
- Reopen task

## Use cases

### Productivity Operations

Use the Worksection API to perform productivity operations programmatically. The API provides 34 endpoints covering core functionality including get all tasks, get project tasks, get task.

Example prompt: Call GET /get_all_tasks to get all tasks

### Automated Comments Management

Automate comments operations by combining multiple Worksection API endpoints. Agents can get project tasks and then get task in a single workflow.

Example prompt: Call GET /get_tasks to get project tasks, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Worksection API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get all tasks', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/get_all_tasks` | Get all tasks |
| GET | `/get_tasks` | Get project tasks |
| GET | `/get_task` | Get task |
| POST | `/post_task` | Create task |
| POST | `/update_task` | Update task |
| POST | `/complete_task` | Complete task |
| POST | `/reopen_task` | Reopen task |
| GET | `/search_tasks` | Search tasks |

## Key resources

- **Comments** — Operations related to Comments
- **Projects** — Operations related to Projects
- **Tasks** — Operations related to Tasks
- **Users** — Operations related to Users

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 50 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/worksection.com/worksection/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Worksection API by hand means passing its API key on every query, resolving your account subdomain host, and signing each request yourself. Through Jentic you install once, import the Worksection API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Worksection API identifies tasks through query and body parameters rather than a resource id in the URL path, so scope by operation: limit the agent to the operations it needs, such as listing or reading tasks. You choose that set, so write actions like posting, completing, or reopening a task are not included unless you add them.
- **Credential handling:** Your Worksection API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get all tasks' or 'search tasks', and Jentic returns the matching Worksection API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the Worksection API use?

The Worksection API uses an API key passed in the `access_token` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get all tasks with the Worksection API?

Yes. Use the GET /get_all_tasks endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Worksection API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get all tasks through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get all tasks'. Jentic returns the matching Worksection API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Worksection API have?

The Worksection API exposes 34 endpoints covering comments, projects, tasks operations.

### Can I limit what my agent is allowed to do with the Worksection API?

Yes. Because you self-host Jentic One, your own rules decide which Worksection API operations and credentials the agent may use. The Worksection API identifies tasks through query and body parameters rather than a resource id in the URL path, so you scope by operation: allow only the calls the agent needs, such as GET /get_all_tasks, GET /get_tasks, or GET /search_tasks for read-only access. Write operations like POST /post_task, /complete_task, and /reopen_task stay out of reach unless you explicitly add them.