DocsReference

Management API

The APIs used by the developer platform web app. Browser requests all go through the /developers/api prefix, for example /developers/api/auth/login.

API Purpose
GET /app/market/dev/works My works
GET /app/market/dev/extensions My plugins and their latest versions
POST /app/market/dev/extensions Create a plugin { key, name }
POST /app/market/dev/extensions/{key}/versions Upload a version (multipart: file, optional changelog)
GET /app/market/dev/tokens My CI publish tokens
POST /app/market/dev/tokens Create a CI publish token
POST /app/market/dev/tokens/{id}/revoke Revoke a CI publish token
GET /app/market/dev/sales/summary Wallet summary
GET /app/market/dev/sales Revenue entries
GET /app/open-api/models Enabled API models and prices
GET /app/open-api/keys My API keys
POST /app/open-api/keys Create an API key (the full key appears only in this response)
PUT /app/open-api/keys/{id} Rename an API key or enable/disable it
POST /app/open-api/keys/{id}/revoke Revoke an API key
GET /app/open-api/usage Usage log (paging with pageNo and pageSize)

Once listed, a plugin appears in the public catalog the desktop app reads, GET /app/market/catalog.json. That endpoint does not go through the developer platform gateway.

These APIs require request signing and can only be called through the platform gateway. To upload versions from scripts or CI, use the publish token from CI publishing; for inference, use the Model API.