AISpeech Office Assistant

Problem Solved

When engineers connect agents to office data, notes, todos, labels, and hot words are often exposed through separate APIs with inconsistent auth, missing scopes, timestamp formats, label uid drift, and error-code handling that all need explicit agreements. AISpeech Office Assistant narrows these interfaces into explicit REST capabilities and establishes predictable boundaries around AIWORK_AUTH_TOKEN persistence and refresh.

How It Works

The core path reads AIWORK_AUTH_TOKEN, then calls /aitablet/api/skill/v2 on ${AIWORK_BASE_URL:-https://aiworks.cn} with Authorization: Bearer ${AIWORK_AUTH_TOKEN}. It covers:
- Notes and groups: list, detail, soft delete, and create or move groups.
- Todos: create, update, delete; beginTime, endTime, and repeatEndTime use millisecond timestamps, and description is the todo description field.
- Label knowledge: read user, note, and todo labels, inspect relations, sync user labels, or bind notes and todos; user label sync reuses historical uid by labelName.
- Databases and hot words: search note/todo personal databases, and query, add, delete, or update hot words.

Boundaries

It is for developers with existing AISpeech Open Platform authorization and does not create tokens. Errors 202401 through 202403 indicate refresh or reinstall authorization; 202404 means missing scopes; 202405 means rate limiting by userId. Callers should verify the token, scopes, and field constraints, such as label element length not exceeding 20.