Skip to report

Brillity Digital · Internal tooling

ManageWP capture

ManageWP has no API. Once a month, run the bookmarklet on each client's History tab and paste what it copies. This page tracks who is done.

Report month
September 2026
Captured
0 of 11 ready
Store
data/managewp

Reviewer notesnot shown to the client

Ready for September 2026

0

Captured after the month closed

Need a recapture

0

Taken on or before the end of September 2026

Never captured

11

No readable data/managewp/<slug>.json

September 2026 events on file

0

Across every capture stored

Every client

Capture status

What is on disk right now, measured against September 2026. A capture has to be taken after the month ends to contain all of it.

ManageWP capture status for September 2026
ClientSeptember 2026 eventsStatus
Raynor Door Authority
raynordoorauthority.com
No capture
Front Range Raynor
frontrangeraynor.com
No capture
Stewart Door
stewartdoor.com
No capture
Quality Overhead Door
qualityohd.com
No capture
Anchor Doors
anchordoors.ca
No capture
Onward Physical Therapy
onwardphysicaltherapy.com
No capture
OnPoint Contracting
onpointcontractingusa.com
No capture
Fowler State Bank
fowlerstate.bank
No capture
Green Lawn Sod
greenlawnsod.com
No capture
MyoLab HQ
myolabhq.com
No capture
Brillity Digital
brillitydigital.com
No capture

Paste

Import a capture

Paste the clipboard. One client's capture or the whole capture-all bundle — the box reads either, and works out which client each one belongs to from its ManageWP site id.

One client’s capture or the whole capture-all bundle — this box reads either. Nothing is written until it validates.

Leave this on detect. Only override it when a client has genuinely moved to a new ManageWP site and the map has not caught up. A bundle ignores this entirely.

The monthly run

Capture every client at once

One click, one bundle, every client. This is the path to use once the site ids are resolved below.

  1. 1. Drag the button onto your bookmarks bar, or copy the URL into a new bookmark.
  2. 2. Open orion.managewp.com/dashboard/websites?type=list and let the list finish loading.
  3. 3. Click the bookmark and leave the tab alone. It matches every client to its ManageWP site, reads each one’s history, and copies a single bundle to your clipboard.
  4. 4. Paste it into the box above. Any client it could not read is reported rather than silently omitted.
Capture all clients

The fallback

Capture one client

For a single site the bundle missed. Install it on your bookmarks bar; it only ever reads the page you run it on.

  1. 1. Show your browser’s bookmarks bar, then drag the button below onto it — or copy the URL and paste it into a new bookmark.
  2. 2. Open the client in ManageWP and go to its History tab.
  3. 3. Click the bookmark. It sets the range to Last 30 Days, reads every page, and copies the capture to your clipboard.
Capture ManageWP

Set up once

Resolve every ManageWP site id

The capture bookmarklet reads its site id from the URL, so someone has to know which of ~146 ManageWP sites belongs to which client. This harvests all of them in one click instead.

  1. 1. Drag the button onto your bookmarks bar, or copy the URL into a new bookmark.
  2. 2. Open orion.managewp.com/dashboard/websites?type=list and let the list finish loading.
  3. 3. Click the bookmark. It reads every page of the list — domain, site id, WordPress version, tags — and copies the lot to your clipboard. Leave the tab alone while it pages through.
  4. 4. Paste it here. Matched clients get their site id written to data/managewp/site-map.json.
Harvest ManageWP site ids

Matching is exact — registrable domain, then any extra domain, then the display name. Nothing fuzzy.

Diagnostic · optional

Find the history endpoint

ManageWP's history table is AngularJS drawing rows from an internal JSON endpoint. Knowing that endpoint would collapse the monthly capture from eleven page walks into eleven fetches.

  1. 1. Drag the button onto your bookmarks bar, alongside the other two.
  2. 2. Open any client’s History tab and click the bookmark. It records for twenty seconds.
  3. 3. While it runs, change the date filter and page through the table — the requests it makes are what we are after.
  4. 4. It copies the captured URLs to your clipboard. Send that to whoever maintains this app; there is no box to paste it into, because it changes code, not data.
Sniff ManageWP requests

This one writes nothing, anywhere. It wraps the page’s own network calls for twenty seconds, then puts them back. It issues no requests of its own and sends nothing off the machine — the output goes to your clipboard and stops there.

What it records is the method, the URL, the status, and the shape of any JSON that comes back: key names and value types, never values. Query parameters whose names look like credentials have their values replaced before anything reaches the clipboard.

If the endpoint turns out to accept a site id and a date range, the monthly ritual on this page stops being a page walk per client and becomes a single button. That is the whole reason this exists — run it once, and the capture step can be upgraded for good.