On July 31, DICloak published the Local API V2 documentation in its help center. The local API runs on a computer with the client open: a script connects to it at 127.0.0.1 using the /openapi/v2 path and a key in the X-API-KEY header. There was no announcement on the blog or channel. On August 7, the company only explained on Telegram how to use the Local API and cloud HTTP API together.
V2 includes 72 methods across nine sections: 19 for profiles (creation, editing, deletion, starting and stopping, and proxy assignment), 9 utility methods (status, version, request limits, browser engine list, and stopping all profiles), 8 each for extensions with bookmarks and members with permissions, 7 for proxies and proxy checks, 6 each for fingerprints and tags, 5 for profile groups, and 4 for cookies (retrieval, import, and clearing). Responses use a consistent format. Some lists can be retrieved by page or cursor. When the request limit is exceeded, the server returns code 429. After a profile starts, the API returns debug_port and web_socket_url for connecting an automation script.
On October 8, a separate guide for managing members was released for the cloud HTTP API: 14 methods, including resetting an internal member's password and issuing a new 2FA key.
In the pricing table, Open API is listed only for Plus (from $28.80 per month) and Share+ (from $138). The key is created in the client under Automation → Open API.
