Skip to main content
These are the routes the Studio panel and the MCP use. The same API tokens and scopes apply.

Publish a version

What happens: DoglyTdc bundles src/, checks syntax, minifies, checks the size (up to 2 MB), encrypts the package and activates the version on the channel. If encryption fails, nothing is published. Response 201:
Errors: UNPROTECTED_CONFIRM (409), VERSION_EXISTS (409), INVALID_FORM_BODY (400, lower number or wrong branch), BUILD_FAILED (400, bundling or syntax error), PAYLOAD_TOO_LARGE (413), SEAL_FAILED (500).

Roll back a version

POST …/studio/releases/{release_id}/rollback makes that version the active one on its channel. Response: { "ok": true, "live": "1.1.0", "channel": "stable" }.

Ban, disable or reactivate

status = active, disabled (with optional until) or banned. It takes effect the next time the person opens the script. The user list shows @username, status, version, site, number of uses, first and last time, and whether the person has active paid access — never the account ID.