Choose an Integration Path
Use this table to pick a path: let AI do the work, call APIs from code, sync data out, or connect other apps without code.
| Your task | Path | What you need | Start here |
|---|---|---|---|
| Let AI create codes, build forms, query records, and check inspection progress | Admin MCP | A CaoLiao account and OAuth authorization for your organization | Quick start |
| Let AI read the public content of a code | Scan-side MCP or A2A | No login | Scan-side quick start |
| Read code content, read and write form records, or query metrics from your own system | API | One OpenAPI Key | API overview |
| Only generate or decode a QR code image | QR code image tools | No authentication | QR code image tools (Chinese only) |
| Generate QR code labels in bulk from your own system | Label Generation API | A label style with API access enabled | Label Generation |
| Notify your system when a new record arrives | Webhook push | A publicly accessible URL | Data sync |
| Put all your data in a database for analysis or BI | Direct database connection | The official database, or your own MySQL 5.7 | Direct database connection |
| Connect CaoLiao to other apps without code | App integrations | An account for the app | Tencent HiFlow, WeCom, Feishu Multi-dimensional Tables, Tencent Docs |
MCP or API
- If AI will make the calls, prefer Admin MCP. It can do more than the API: create codes, create sub-codes in bulk, build forms and recurring tasks, and download labels. See Tools.
- To submit records to a form or verify certificates, use the API. These two operations are not among the default Admin MCP tools. See Add record and Verify record certificate.
- You can use both. Let AI build the content through MCP, then have your business system read and write records through the API.
About app integrations
These integrations are configured by pointing and clicking in the backend, with no code. For WeCom edition purchasing and common questions, see WeCom edition features.
If you already use the dynamic QR code API v1
The old APIs still work but are no longer updated. New projects should go straight to the API Reference. Existing projects can switch gradually using the migration table.