System and Auth

Public health, API key auth, operator status, configuration, logs, keys, and proxy management routes.

by @saifyxpro

Auth header


All protected routes use:

Pick the right credential

External scripts, SDKs, workflow tools, CLI calls, and MCP clients should always use a normal API key created from the dashboard. DASHBOARD_INTERNAL_API_KEY is for the dashboard proxy path only.

Public endpoint


MethodPathPurpose
GET/api/healthpublic health check and route summary

Operator status


MethodPathPurpose
GET/api/operators/statuslist all operators and their current availability

Config endpoints


MethodPathPurpose
GET/api/configread current runtime settings
PATCH/api/configupdate runtime settings and restart browser runtime

Typical config areas include browser timeout, concurrency, and Camoufox behavior.

Dashboard and logs


MethodPathPurpose
GET/api/dashboard/statsread dashboard summary metrics
GET/api/logslist paginated request logs
GET/api/logs/statsread aggregated request log stats

API key management


MethodPathPurpose
GET/api/keyslist API keys
POST/api/keyscreate API key
PATCH/api/keys/:id/revokerevoke API key
DELETE/api/keys/:iddelete API key

Proxy management


MethodPathPurpose
GET/api/proxieslist all proxies
GET/api/proxies/activelist active proxies only
GET/api/proxies/:idread one proxy
POST/api/proxiescreate proxy
PATCH/api/proxies/:idupdate proxy
DELETE/api/proxies/:iddelete proxy
POST/api/proxies/:id/toggletoggle active state
POST/api/proxies/:id/testtest proxy connectivity

Operational notes


  • the dashboard can use DASHBOARD_INTERNAL_API_KEY on server-side proxy calls
  • external clients should always use a normal API key
  • stored secrets should not be returned raw in responses

Related Docs