Some capabilities are already available: API, Webhooks, task scripts, and device access. Some are still being developed: template market, service provider directory, and application shelves. This page separates the two, You can start with the parts that can be used now, without waiting for the entire plan to be implemented.
Correspond according to what you can provide, not by company type.
Integrate account, environment, publishing, and session capabilities into your own system, or make an upper-level tool for specific scenarios.
For services such as agency operation, account maintenance, and private domain follow-up, using the platform as a delivery tool is more efficient than building several sets of tools yourself.
Account maintenance strategy templates, character and vocabulary libraries, industry content templates, and collection scripts are all experience-based assets that others are willing to use directly.
These items are available now and are not within the scope of preparation.
Apply for and manage keys in the background, assign multiple keys according to purpose, and revoke them at any time.
Interface list, parameter description, request examples and error codes. Organized by modules and corresponding to backend functions.
Task status changes, publishing results, and session events can be called back to your address without polling.
Submit a publishing task through the interface, specify the account, content and time, and the results are returned to your system.
Owned devices can be connected to unified management through MQTT and included in the account and task system.
Write repeated operations as scripts and execute them in the environment. They can be triggered on a schedule or called by an interface.
These have not been done yet, and there is no set time. It's listed to give you direction, not as a commitment.