Skip to content
PowerOps
Browse the help centre

Automation

Drive profiles from code

The Local API, its bearer key, attaching Playwright or Puppeteer to a running profile, and working through large jobs in batches.

Guide · 1 min read

The Local API

PowerOps serves a local HTTP API on http://127.0.0.1:50326 whenever it is running. It binds to loopback only, so nothing on your network can reach it and every request comes from the same machine PowerOps runs on. The full route list and examples live on the Local API page.

Read the Local API page

The bearer key

Every route except status requires a bearer key in the Authorization header. The status route stays open so a script can check that PowerOps is up before it authenticates. An owner or admin copies the key from API in the sidebar. Treat it like any other secret and keep it out of committed code.

Attach with Playwright or Puppeteer

Ask the API to start a profile's browser. The response includes the CDP WebSocket endpoint for that browser. Connect Playwright or Puppeteer over that endpoint and the script drives the session with the profile's own identity and proxy in place. When the script is done, close the browser so state is written out.

Batch patterns

Each open profile is its own browser process, so memory is the practical ceiling. Work through large jobs a few profiles at a time. Open a small batch, do the work, close it cleanly, then start the next. Closing between batches is also when Cloud Sync uploads each session, unless it has been switched off.

Try it on your own computer

PowerOps is a Windows download. Install it, sign in with your ArticleOps account, and the getting started guide takes you from there to your first open profile.