DingTalk Document (adoc) API Guide

Portal: https://alidocs.dingtalk.com

Programmatic access to DingTalk native documents. No stable public OpenAPI exists for the read paths the web app uses for native docs. This skill mirrors the browser with cookie-based session auth and internal endpoints reverse-engineered from the web frontend.

Official SDK vs This Skill

Alibaba ships Open Platform SDKs (alibabacloud-dingtalk, dingtalk-sdk) for server APIs: app credentials, access_token, messaging, org/contacts, calendar, etc. Those SDKs do not cover alidocs.dingtalk.com native-document reads — auth is app-based (not browser-cookie-based) and the adoc/knowledge-base endpoints are not exposed as stable public OpenAPIs.

When to use this skill (cookie-based):

• Individual developer or ad-hoc automation — no enterprise app registration or admin approval needed
• Custom/branded DingTalk deployments where open APIs for documents may not exist
• Read-only access that mirrors "what the user can open in the browser"

When to use the official SDK (app-based):