Chatwork API

Name: Chatwork API
Brand: Chatwork API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsChat MessagingapiKey32 EndpointsREST

For Agents

Post messages, create tasks, manage rooms, and upload files in Chatwork so an agent can run team chat workflows end to end.

Install Jentic One Beta

Connect the Chatwork API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Chatwork API, 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 Chatwork API.

Post and update messages in any Chatwork group chat room

Create and complete tasks tied to specific rooms and assignees

Provision new group chat rooms with members and roles

Upload files to rooms and fetch file metadata

GET STARTED

Start building with Chatwork API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Chatwork API, keeping it validated and agent-ready. Chatwork is a Japan-headquartered business chat platform used by hundreds of thousands of companies for team messaging, task management, and file sharing inside group chat rooms. The v2 REST API exposes 32 endpoints covering rooms, messages, tasks, files, contacts, and invitation links — enough to fully automate room creation, message posting, task tracking, and file uploads. It is well suited to teams building bots, integrations, or migration tools on top of Chatwork.

Use Cases

Patterns agents use Chatwork API for, with concrete tasks.

★ Project Room Bot

Run a bot that posts daily standup prompts, creates tasks from meeting notes, and uploads weekly reports into a project's Chatwork room. The bot uses POST /rooms/{room_id}/messages to send updates, POST /rooms/{room_id}/tasks to file action items, and POST /rooms/{room_id}/files to share artefacts — turning Chatwork into the project's operational hub.

Post 'Daily standup at 10:00' to room_id 12345 and create three tasks for users 100, 101, 102 due tomorrow.

Task Automation

Mirror tasks between Chatwork and an external project tracker. Pull /my/tasks for the current user, sync new items into the tracker, and create matching tasks in Chatwork with POST /rooms/{room_id}/tasks when issues are filed elsewhere. Useful for teams that live in Chatwork but report into Jira or Linear.

Fetch /my/tasks and return the count of incomplete tasks due in the next 7 days.

Onboarding and Room Provisioning

When a new project starts or a new hire joins, automatically create a Chatwork room, invite the right members, and post a welcome message with onboarding links. POST /rooms creates the room, PUT /rooms/{room_id}/members updates membership, and POST /rooms/{room_id}/link generates a shareable invite for guests.

Create a room called 'Project Atlas Kickoff' with members [100, 101, 102] as admin and post a welcome message.

AI Agent for Chatwork Workflows

An autonomous agent reads unread Chatwork rooms, drafts replies based on prior context, files action items as tasks, and posts them — all through Jentic without holding the X-ChatWorkToken in agent memory. Jentic's intent search lets the agent pick from 32 endpoints with one query.

Through Jentic, search 'post a message to a chatwork room', load the schema, and execute with room_id 12345 and body 'Acknowledged'.

Key Endpoints

32 endpoints — jentic publishes the only available openapi specification for chatwork api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/rooms/{room_id}/messages

Post a message to a room

GET

/rooms/{room_id}/messages

Get messages in a room

POST

/rooms/{room_id}/tasks

Create a task in a room

GET

/my/tasks

Get your task list

POST

/rooms

Create a new group chat room

POST

/rooms/{room_id}/files

Upload a file to a room

GET

/me

Get your account information

POST

/rooms/{room_id}/messages

Post a message to a room

GET

/rooms/{room_id}/messages

Get messages in a room

POST

/rooms/{room_id}/tasks

Create a task in a room

GET

/my/tasks

Get your task list

POST

/rooms

Create a new group chat room

Why Jentic?

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

Credential isolation

Chatwork X-ChatWorkToken values are stored encrypted in the Jentic MAXsystem vault. The agent never holds the raw token — Jentic injects it into the header at execution time.

Intent-based discovery

Agents search Jentic by intent (e.g. 'post a message to a chatwork room') and Jentic returns the matching Chatwork operation with its input schema, so the agent picks among 32 endpoints without reading docs.

Time to first call

Direct Chatwork integration: about a day for token setup, room/message handling, and pagination. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Chatwork API through Jentic.

Why is there no official OpenAPI spec for Chatwork API?

Chatwork does not publish an OpenAPI specification on its developer site. Jentic generates and maintains this spec so that AI agents and developers can call Chatwork API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Chatwork API use?

Chatwork uses an API key passed in the X-ChatWorkToken header. Tokens are generated per user from the Chatwork account settings page. Through Jentic, the token is stored encrypted in the MAXsystem vault and injected at execution time, so agents never see the raw value.

Can I post messages to a Chatwork room with the API?

Yes. POST /rooms/{room_id}/messages accepts a body parameter and posts the message to the specified room. Chatwork supports its own [To:] and [info] tags inside message bodies for mentions and styling.

How do I create a task in Chatwork via the API?

Use POST /rooms/{room_id}/tasks with the body, assigned account ids (to_ids), and an optional limit timestamp. The endpoint returns the created task ids, which you can later mark complete via PUT /rooms/{room_id}/tasks/{task_id}.

What are the rate limits for the Chatwork API?

The OpenAPI specification does not declare formal rate limits. Chatwork enforces per-token throttling on its production servers — plan for retry-with-backoff on 429 responses and batch reads where possible.

How do I post a message to Chatwork through Jentic?

Install the SDK with `pip install jentic`, then call Jentic.search('post a message to a chatwork room'), load the schema for /rooms/{room_id}/messages, and execute with the room_id and body. Jentic handles X-ChatWorkToken injection automatically.

Chatwork API

Connect the Chatwork API to your agent

Capabilities

Start building with Chatwork API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs