Larksuite Lark Open Platform API

Name: Lark Open Platform API
Brand: Lark Open Platform API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationbearer24 EndpointsREST

For Agents

Send Lark messages, manage chats and contacts, schedule calendar events, and route approvals across the Lark workspace.

Install Jentic One Beta

Connect the Lark Open Platform API to your agent

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

Send a direct or group message in Lark Messenger

Create or fetch a Lark chat and manage its member list

Look up Lark users and departments by ID

Create, update, or fetch calendar events on a user's Lark calendar

GET STARTED

Start building with Lark Open Platform API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Lark Open Platform API for, with concrete tasks.

★ Internal Notifications and Alerts

An ops or product team posts deployment, incident, and KPI notifications into a dedicated Lark group chat by calling the messaging endpoints. The API accepts text and rich card payloads, so notifications can include action buttons that link back to internal tools. This keeps the engineering team aligned without leaving Lark.

POST a Lark message containing the deploy version, commit, and a 'view logs' button to the #ops-alerts chat using its chat_id, then confirm delivery.

Onboarding and Directory Lookups

An onboarding workflow looks up a new joiner's Lark user record and department to grant downstream access and post a welcome message in the team chat. The contact endpoints expose users and departments by ID so internal tools can mirror the Lark org chart. Useful for HRIS-to-collab sync without a custom directory.

GET the user record for the new joiner from /contact/v3/users, then POST a welcome message to their team chat tagging them.

Calendar and Approval Automation

A workflow tool schedules meetings on a user's Lark calendar and routes related approvals through the Lark Approvals service. Calendar endpoints accept event details and attendees, while approval endpoints submit and track requests against a configured approval template. This automates the meet-then-approve pattern common in operations.

Create a 30-minute calendar event in /calendar/v4/calendars/{id}/events with the listed attendees, then submit a related approval request that references the meeting outcome.

AI Agent Workspace Assistant

An AI agent answers user questions and performs Lark actions on their behalf — sending messages, scheduling events, and submitting approvals — by calling the Lark Open Platform API through Jentic. The agent searches Jentic for messaging or calendar operations, loads the schema, and executes the call without manually wiring Lark tenant tokens. This turns Lark into a tool surface for agent workflows.

Use Jentic to send a Lark message to the user's manager confirming the agent has scheduled the requested meeting and submitted the approval, then return the message_id to the user.

Key Endpoints

24 endpoints — jentic publishes the only available openapi specification for lark open platform api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/im/v1/messages

Send a message in Lark Messenger.

GET

/im/v1/messages/{message_id}

Retrieve metadata for a specific message.

POST

/im/v1/chats

Create a new chat.

GET

/im/v1/chats/{chat_id}/members

List members of a chat.

GET

/contact/v3/users/{user_id}

Get a Lark user record.

GET

/contact/v3/departments

List departments in the organisation.

GET

/calendar/v4/calendars

List the user's calendars.

POST

/calendar/v4/calendars/{calendar_id}/events

Create a calendar event.

POST

/im/v1/messages

Send a message in Lark Messenger.

GET

/im/v1/messages/{message_id}

Retrieve metadata for a specific message.

POST

/im/v1/chats

Create a new chat.

GET

/im/v1/chats/{chat_id}/members

List members of a chat.

GET

/contact/v3/users/{user_id}

Get a Lark user record.

Why Jentic?

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

Credential isolation

Lark app credentials and tenant_access_tokens are stored encrypted in the Jentic vault. Agents receive scoped Bearer tokens at execution time so the underlying app_secret never enters the agent context.

Intent-based discovery

Agents search by intent (e.g., 'send a lark message') and Jentic returns the matching Lark Open Platform operation with its input schema, so the agent can call the right endpoint without browsing Lark docs.

Time to first call

Direct Lark integration: 2-3 days to wire app auth, token refresh, and per-endpoint payload shapes. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Lark Open Platform API through Jentic.

Why is there no official OpenAPI spec for Lark Open Platform API?

Lark does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Lark Open Platform 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 Lark Open Platform API use?

The API uses Bearer auth — typically a tenant_access_token or user_access_token issued from a Lark app's app_id and app_secret. Through Jentic, those credentials live in the encrypted vault and the agent only sees a scoped Bearer token at execution time.

Can I send a message to a Lark group chat with the Lark Open Platform API?

Yes. POST to /im/v1/messages with receive_id_type='chat_id' and the chat's id, plus a text or interactive card payload. The response returns the message_id which can be passed to /im/v1/messages/{message_id} for delivery confirmation.

What are the rate limits for the Lark Open Platform API?

Lark applies per-app and per-tenant rate limits that vary by endpoint and are not enumerated in the spec. Messaging and contact endpoints typically have stricter limits than read-only lookups; check the Lark Open Platform docs for current per-endpoint quotas.

How do I schedule a Lark calendar event through Jentic?

Search Jentic for 'schedule a lark calendar event', load the operation schema, and POST to /calendar/v4/calendars/{calendar_id}/events with the event title, start, end, and attendees.

Can I submit approval requests with the Lark Open Platform API?

Yes. The Approvals endpoints submit a request against a configured approval template and return its instance_code so the workflow can poll for approve or reject decisions.

Larksuite Lark Open Platform API

Connect the Lark Open Platform API to your agent

Capabilities

Start building with Lark Open Platform API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs