Feishu OpenPlatform Server SDK for Python

中文

The Feishu Open Platform provides server-side APIs for messaging, contacts, approval, sheets, Base, and many other product capabilities. This SDK wraps the repeated platform work around API calls, including token management, request signing, encryption/decryption, event dispatching, and typed request/response models.

Documentation

Installation

pip install lark-oapi

Python 3.8 or later is required.

Basic Usage

import lark_oapi as lark
from lark_oapi.api.im.v1 import *

client = lark.Client.builder() \
    .app_id("cli_xxx") \
    .app_secret("your_app_secret") \
    .build()

request = CreateMessageRequest.builder() \
    .receive_id_type("chat_id") \
    .request_body(CreateMessageRequestBody.builder()
        .receive_id("oc_xxx")
        .msg_type("text")
        .content("{\"text\":\"hello world\"}")
        .build()) \
    .build()

response = client.im.v1.message.create(request)

ClientAssertion Keyless Mode

For self-built apps that use an external signing service, the SDK can fetch tenant tokens with client_assertion instead of app_secret. The SDK does not generate, parse, sign, or store JWT private keys; your provider supplies the final assertion string.

import os

import lark_oapi as lark
from lark_oapi.core.client_assertion import ClientAssertionToken


class EnvClientAssertionProvider:
    def retrieve_token(self, aud: str) -> ClientAssertionToken:
        return ClientAssertionToken(os.environ["LARK_CLIENT_ASSERTION"])


client = lark.Client.builder() \
    .app_id(os.environ["LARK_APP_ID"]) \
    .client_assertion_provider(EnvClientAssertionProvider()) \
    .build()

If you use a custom OpenAPI domain, also configure oauth_base_url(...) so the SDK can derive the OAuth audience correctly. Keyless mode is for self-built apps only and does not support AppAccessToken-only APIs.

One-Click App Registration

lark_oapi.register_app creates an app through the OAuth device flow. It returns a verification URL in on_qr_code; render the URL as a QR code or show it as a link for the user to open in Feishu/Lark.

import lark_oapi as lark

def on_qr_code(info):
    print(info["url"])


result = lark.register_app(
    on_qr_code=on_qr_code,
    app_preset={
        "avatar": [
            "https://example.com/a.png",
            "https://example.com/b.webp",
        ],
        "name": "{user}'s app",
        "desc": "Created by the business platform",
    },
)

print(result["client_id"])

Custom scopes/events/callbacks and updating an existing app

When creating an app, use addons to incrementally request scopes, event subscriptions, and callbacks on top of the platform base template. They are pre-filled into the confirm page shown after the user scans the QR code, and take effect once the user confirms:

result = lark.register_app(
    on_qr_code=on_qr_code,
    addons={
        "scopes": {
            "tenant": ["im:message:send_as_bot"],
            "user": ["calendar:calendar:read"],
        },
        "events": {"items": {"tenant": ["im.message.receive_v1"]}},
        "callbacks": {"items": ["card.action.trigger"]},
    },
    create_only=True,
)

lark.register_app(
    on_qr_code=on_qr_code,
    app_id="cli_xxx",
    addons={"scopes": {"tenant": ["drive:drive.metadata:readonly"]}},
)

Notes:

addons is additive only: items are merged on top of the base template; base permissions can never be removed.
addons.preset picks the base template: omitted or True keeps the default base template, while False switches to the minimal base template so the final config only contains what addons declares. With "preset": False, an addons without any incremental item is also valid.
Only the 5 public config types are supported: tenant/user scopes, tenant/user events, and callbacks. Sensitive config such as event request URLs, security.*, or encrypt keys cannot travel through addons.
The SDK validates the shape, not the item names; names unknown to the platform catalog are ignored by the confirm page.

For a real manual E2E run without mocked registration responses:

python3 samples/registration/app_preset_live_e2e.py --open

`register_app` parameters

Parameter	Description	Type	Required	Default
`on_qr_code`	Callback when the verification URL is ready. Receives `{"url": str, "expire_in": int}`	function	Yes	-
`on_status_change`	Callback on polling status changes. Status values include `polling`, `slow_down`, `domain_switched`	function	No	-
`source`	Source identifier appended to the QR URL as `python-sdk/{source}`	string	No	`python-sdk`
`cancel_event`	`threading.Event` used to cancel sync polling	threading.Event	No	-
`domain`	Custom Feishu accounts base URL	string	No	`https://accounts.feishu.cn`
`lark_domain`	Custom Lark accounts base URL used when tenant brand is Lark	string	No	`https://accounts.larksuite.com`
`app_preset`	Pre-fill values for the app-creation page. All fields are optional; users can still edit them on the page. Pass raw values; the SDK URL-encodes them automatically	dict	No	-
`app_preset.avatar`	App avatar URL(s). 1-6 URLs supported; the first one is selected by default. Allowed formats are handled by the Web page: png / jpg / jpeg / webp / gif	string or list[string]	No	-
`app_preset.name`	App name. Supports the `{user}` placeholder, replaced by the Web page with the scanning user's name	string	No	-
`app_preset.desc`	App description. Supports the `{user}` placeholder	string	No	-
`addons`	Incremental scopes/events/callbacks pre-filled into the confirm page, effective after user confirmation	dict	No	-
`addons.preset`	Base template switch. Omitted or `True` keeps the default base template; `False` switches to the minimal base template so the app only carries the configs explicitly declared in `addons`	bool	No	`True`
`addons.scopes.tenant`	App-identity scopes, e.g. `im:message:send_as_bot`	list[string]	No	-
`addons.scopes.user`	User-identity scopes, e.g. `calendar:calendar:read`	list[string]	No	-
`addons.events.items.tenant`	App-identity events, e.g. `im.message.receive_v1`	list[string]	No	-
`addons.events.items.user`	User-identity events, e.g. `calendar.calendar.event.changed_v4`	list[string]	No	-
`addons.callbacks.items`	Callbacks, e.g. `card.action.trigger`	list[string]	No	-
`create_only`	When `True`, the landing page only allows creating a new app and hides the select-existing-app entry. Takes precedence over `app_id` when both are set	bool	No	-
`app_id`	App ID (`cli_` prefix) of an existing app. When set, the flow updates that app's config; carried on the QR URL as `clientID`	string	No	-

Legacy Channel Module

lark_oapi.channel is the legacy Channel entry point kept for compatibility during the migration window. New Channel features ship in lark-channel-sdk with the lark_channel import path; critical fixes for existing lark_oapi.channel users are evaluated for backport until 2027-06-02.

lark-channel-sdk can be installed alongside lark-oapi. Its SecurityConfig defaults to compatibility mode so migrated bots can roll out with audit mode before strict enforcement. See the migration guide for the full checklist.

pip install lark-channel-sdk

from lark_channel import FeishuChannel

Existing legacy import example:

import asyncio
import os

from lark_oapi.channel import FeishuChannel

channel = FeishuChannel(
    app_id=os.environ["LARK_APP_ID"],
    app_secret=os.environ["LARK_APP_SECRET"],
)

async def on_message(msg):
    await channel.send(
        msg.chat_id,
        {"text": f"echo: {msg.content_text}"},
    )

channel.on("message", on_message)

asyncio.run(channel.connect())

Channel documentation:

Examples

More composite API examples and business scenario samples are available in oapi-sdk-python-demo.

License

MIT

Contact Us

Click Server SDK in the upper right corner of the documentation page and submit feedback.

Webhook authentication

When no EncryptKey is configured and a nonempty VerificationToken is explicitly supplied, the SDK validates the token before invoking event or callback handlers: top-level token for v1 and header.token for v2. Missing, null, empty, non-string, or mismatched tokens are rejected. Challenge responses also validate explicitly configured verification tokens.

Leaving both credentials empty retains the previous behavior. Encrypted events retain existing decryption and signature checks, and WebSocket clients continue using trusted internal dispatch.

Rollback: reverting this change restores the validation gap for explicitly configured VerificationTokens. Keep independent webhook authentication in place before rolling back.

Runtime webhook credentials

handler = (lark.EventDispatcherHandler.builder("", "")
    .webhook_credentials_provider(credential_store.get_webhook_credentials)
    .build())

The provider is called once per HTTP webhook (events, callbacks, and challenge), before decryption and validation. It is not called while building the handler or by trusted WebSocket dispatch. The returned pair overrides static credentials for that request only; the next request sees updates. The example store method returns a lark.WebhookCredentials value and reads the complete pair atomically from a thread-safe local cache. Providers must return promptly, with caller-owned timeouts for any I/O. Empty strings retain legacy empty-configuration behavior. Invalid results and exceptions reject the request without static fallback, and original exception details are not logged or returned. Provider registration is initialization-only. Monitor acquisition latency and failures in the provider. Remove the provider registration to return to static credentials.

Metadata

Release files for lark-oapi 1.7.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lark-oapi 1.7.4
File	Size	Uploaded
lark_oapi-1.7.4.tar.gz	2.3 MB	Oct 12, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for lark-oapi 1.7.4
File	Interpreter	ABI	Platform	Reset
lark_oapi-1.7.4-py3-none-any.whl 7.7 MB Oct 12, 2026	Python 3	none	any	Details

Total release size: 10.1 MB

Release files / lark_oapi-1.7.4.tar.gz

Download URL	lark_oapi-1.7.4.tar.gz
Size	2.3 MB
Tags	Source
SHA-256 checksum How to use checksums	`eb2347b6dc5e69b3863fa112417f025ceb8ec9c37c3fe26ca5acc2c6b62fa780`
BLAKE2b-256 checksum How to use checksums	`fb8e05eeb3014922cc8b9f5e8a666738e9a4afe41f6ebdb3cd3aeb8d070a6a88`
Upload date	Oct 12, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/6.2.0 CPython/3.9.6`

Release files / lark_oapi-1.7.4-py3-none-any.whl

Download URL	lark_oapi-1.7.4-py3-none-any.whl
Size	7.7 MB
Tags	Python 3
SHA-256 checksum How to use checksums	`7b39f7a862faecc94e574df21ad668b8aa005a3f5caa6e4580d05139a72c84e2`
BLAKE2b-256 checksum How to use checksums	`9b2dd80b970ac77e43b40aa972b3fe79da07e491cfd4eb2067367c2e01d00169`
Upload date	Oct 12, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/6.2.0 CPython/3.9.6`