awork API v1

✓ Official Vendor SpecProductivityTask Managementoauth2672 EndpointsREST

For Agents

Manage projects, tasks, time entries, planner bookings, and absences in awork so agents can drive end-to-end agency and services workflows.

Install Jentic One Beta

Connect the awork API v1 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the awork API v1, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with awork API v1 API.

Create, update, and transition projects with task lists, members, and templates via /projects endpoints

Manage tasks across projects including assignments, dependencies, priorities, and tags

Log and retrieve time entries against tasks and projects through awork's time-tracking endpoints

GET STARTED

Start building with awork API v1 API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use awork API v1 API for, with concrete tasks.

★ Project Setup from Templates

Agencies start every engagement from a project template covering tasks, sections, and roles. The /projects/templates endpoints let an agent clone a template into a new project for a specific client and team, replacing 30-45 minutes of clicking through the awork UI per new engagement.

Create a project named 'Acme Brand Refresh' for client {id} from template {templateId}, assign three named team members, and return the new project ID

Time Tracking and Capacity Monitoring

Operations teams use awork's time-tracking endpoints to capture time entries and the planner endpoints to compare booked capacity against logged time. Surfacing under- or over-utilisation early means staffing decisions happen before deadlines slip rather than after.

Pull the last week's time entries grouped by user and compare to that week's planner bookings; flag users with more than 20% deviation

Task Triage and Prioritisation

Project managers use the /tasks endpoints to list, filter, and reassign tasks across projects so agents can triage the team's workload. Filters by tag, priority, status, and assignee mean an agent can pull 'overdue and blocked' tasks across the workspace and act on them in bulk.

List all tasks across active projects tagged 'blocker' with due dates in the past, then post each to the assignee's chat as a reminder

Absence and Resource Planning

HR-light operations and resourcing leads manage absences and planner bookings through awork's absence and planner endpoints. The data feeds capacity views so project managers can plan around vacations and sick days without spreadsheets.

Add a vacation absence for user {id} from 2026-07-10 to 2026-07-21, then list any planner bookings overlapping that range and notify the project owners

Agent-Driven Project Operations via Jentic

AI agents handling project status, time logging, and planner updates call awork through Jentic so a single conversational request can update tasks, log time, and adjust schedules without bouncing between tools. Jentic exposes the 672 awork operations as discoverable tools indexed by intent.

Given a Slack message 'log 1.5h on the Acme website task yesterday', search Jentic for 'log time entry awork', load the schema, and post the time entry against the matching task

Key Endpoints

672 endpoints — the awork api is the integration surface for awork's project management, time tracking, and team collaboration platform aimed at agencies and professional-services teams.

METHOD

PATH

DESCRIPTION

GET

/projects

List projects in the workspace

GET

/projects/{projectId}

Retrieve a project by ID

POST

/projects/{projectId}/changestatus

Change a project's status

POST

/projects/{projectId}/members

Add a member to a project

POST

/projects/batch/{operation}

Run a batch operation across projects

GET

/projects/key/{projectKey}

Retrieve a project by its short key

GET

/projects

List projects in the workspace

GET

/projects/{projectId}

Retrieve a project by ID

POST

/projects/{projectId}/changestatus

Change a project's status

POST

/projects/{projectId}/members

Add a member to a project

POST

/projects/batch/{operation}

Run a batch operation across projects

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

awork OAuth client credentials and refresh tokens are stored encrypted in the Jentic vault. Jentic refreshes bearer tokens automatically and attaches them to each request — agents never handle raw tokens.

Intent-based discovery

Agents search by intent (e.g., 'log a time entry' or 'create a project from a template') and Jentic returns the matching awork operation from the 672 available, with the full request and response schemas drawn from the OpenAPI spec.

Time to first call

Direct awork integration: 1-2 weeks for OAuth, schema mapping across the large surface, and pagination handling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using awork API v1 API through Jentic.

What authentication does the awork API use?

The awork API uses OAuth 2.0 with bearer tokens. Your application authenticates against awork's identity provider, receives a token, and includes it as 'Authorization: Bearer <token>' on each call. Through Jentic, OAuth credentials and refresh tokens live in the Jentic vault and tokens are refreshed automatically.

Can I create projects from templates with the awork API?

Yes. awork exposes project-template endpoints so an agent can clone a template into a new project complete with task lists, sections, and default assignments. Pair this with /projects/{projectId}/members to attach the project team in the same flow.

What are the rate limits for the awork API?

awork applies per-workspace throttling that scales with subscription tier; bursts beyond a few requests per second can return HTTP 429. Watch the response headers for retry guidance and prefer the batch endpoints under /projects/batch/{operation} for bulk changes rather than per-record loops.

How do I log a time entry through Jentic?

Search Jentic for 'log a time entry awork', load the schema for the awork time-entry endpoint, and execute with the user, task, date, and duration. Jentic returns the matching operation so the agent does not have to traverse 672 paths to find it.

Does the awork API expose absences and planner bookings?

Yes. awork's absence endpoints record vacations, sick days, and other absences per user, and the planner endpoints book users onto projects across days or hours. Together they keep capacity reporting accurate without separate HR or scheduling tools.

Is there a sandbox for the awork API?

awork does not publish a separate sandbox tenant. The standard pattern is to create a free trial or test workspace, generate OAuth credentials in that workspace, and develop against it before pointing your integration at the production workspace.

awork API v1

Connect the awork API v1 to your agent

Capabilities

Start building with awork API v1 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs