How to Export Wachete Monitoring History

To export recent Wachete monitoring values, open the monitors view, select up to 20 monitors, and click Export. Wachete says the resulting Excel file contains the last 100 values for each selected monitor. For date-filtered or additional results, use Wachete’s data-list API endpoint. If you need an inventory of URLs rather than historical values, use Profile → Account → Export monitored URLs.

Choose the export that matches what you need

What you need	Wachete option	What it contains
Recent observed values	Monitors view → select monitors → Export	Excel file with the last 100 values per selected monitor; up to 20 monitors at once
Every monitored URL in the account	Profile → Account → Export monitored URLs	Excel URL inventory, including a Dynamic Monitor column
Monitor URLs and names to edit or re-import	Select monitors → Edit → Export	Text list of URLs and monitor names, suitable for pasting into multi-edit
A date range or more API result batches	Wachete REST API data-list endpoint	Monitor content values with optional date bounds and continuation-token pagination

The URL inventory and multi-edit exports are not history exports. Choose the selected-monitor Export or API when you need the recorded values.

Export the latest values from the Wachete interface

Sign in to Wachete and open the monitors view.
Use the checkbox at the lower right of each monitor row to select the monitors you want.
Select no more than 20 monitors for this export.
Click Export at the top of the view.
Open the generated Excel file and check that it contains the monitors and values you intended to save.

The documented export includes the last 100 values for each selected monitor. The FAQ does not establish that another interface action exports every retained value for one monitor, so do not assume this spreadsheet is a complete archive.

Export an account-wide URL inventory

Open Profile.
Go to Account.
Choose Export monitored URLs.
Save the Excel file and use its Dynamic Monitor column when you need to distinguish dynamic monitors.

This export is useful for reviewing what is monitored or maintaining an inventory. Wachete describes it as a list of URLs, not as a history of observed content values.

Export monitor definitions for editing or re-import

Select the monitors in the monitors view.
Click Edit to open the multi-edit window.
Click Export in that window.
Save the resulting text containing monitor URLs and names.

You can paste that text into the multi-edit text box to import monitors again. It contains monitor definitions, not the historical value series.

Retrieve a date range or further batches with the API

Wachete documents this endpoint for a monitor’s content values:

GET https://api.wachete.com/thirdparty/v1/data/list/{ID_OF_YOUR_WACHET}

The API documentation describes optional from and to ISO-format date bounds, returnDiff=true to request differences rather than only values, and continuationToken to request the next batch. It uses bearer-token authentication. Obtain the token through Wachete’s API login endpoint with the credentials available from your Wachete profile, following the official API documentation.

The dossier’s official API documentation does not provide a complete copy-and-run export script, establish an exact response schema or export format, or say that API access bypasses plan-dependent retention. Treat the endpoint as a documented retrieval path and use the current Wachete API documentation for the precise login request, response fields, and continuation-token response shape.

API retrieval checklist

Use the monitor ID in place of {ID_OF_YOUR_WACHET}.
Authenticate with the bearer token obtained using Wachete’s documented login flow.
Pass from and to in the documented ISO time format when limiting the range.
Set returnDiff=true only when differences are what you need.
When the response provides a continuation token, request the next batch with that token; continue until no next token is returned.
Keep the raw responses until you have confirmed the date range and all pages were retrieved.

Do not guess a timezone for export timestamps: the reviewed sources do not specify the timezone or the exact timestamp columns for each export.

Understand retention and timestamps

Wachete advertises up to 12 months of history, with the actual retention depending on the plan. An export cannot be assumed to include records outside the available retention window. The documentation reviewed also distinguishes a monitor’s last-checked time from its last-changed time. A check timestamp tells you when Wachete checked; it does not by itself prove that the monitored content changed then.

Troubleshooting

Problem	Likely cause	What to do
The spreadsheet has URLs but no history values	You used Export monitored URLs, which is an inventory export.	For values, select monitors in the monitors view and use its Export action, or retrieve values through the API.
A selected-monitor export omits older records	The documented UI export contains only the last 100 values per selected monitor.	Use the API’s date bounds and continuation-token pagination for additional available records. Retention still depends on plan.
You cannot select more monitors for one export	The documented selected-monitor export supports up to 20 at a time.	Export in groups of 20 or fewer.
The text export cannot be opened as a history spreadsheet	The multi-edit Export is a text list of URLs and names.	Use it for monitor definitions or re-import. Use the selected-monitor export for recent values.
An API request is unauthorized	The bearer token may be missing, invalid, or obtained incorrectly.	Repeat Wachete’s documented API login flow using the credentials from your profile, then send the returned token as a bearer token.
An API date-range request returns an incomplete set	More results may be available through continuation-token pagination, or the requested dates may exceed retained history.	Follow each continuation token and check that the requested period falls within your plan’s available retention.
A timestamp looks like a change time but the value did not change	Last checked and last changed are different events.	Interpret the field according to its label; do not treat a check time as proof of a content change.

Performance, reliability, and recordkeeping

For a quick spreadsheet: use the UI export. Split selections into batches of at most 20 monitors.
For larger or date-bounded retrieval: use the API’s continuation token to page through results instead of assuming one response is complete.
Preserve provenance: retain the original export and note the monitor, requested dates, and retrieval date alongside any transformed data.
Check completeness: verify the selected monitor set, date bounds, and that pagination finished. The available documentation does not specify a checksum or completeness report.
Plan for retention: Wachete states history can be retained for up to 12 months depending on plan. Export important records before they age out of the available history.

No API pricing, throughput limits, or response-time figures are established by the reviewed sources, so estimate retrieval cost and duration from your account and current Wachete plan rather than assuming a fixed rate.

Or skip the browser setup

If your task is to capture how a monitored page looks, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. It accepts cookie banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. AI agents can use its MCP server tools: take_screenshot, get_page_info, and capture_pdf.

See the ScreenshotNeo API documentation for the request options. This runnable cURL example saves a WebP screenshot:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Free includes 1,000 screenshots a month with no card. Paid plans start at $5 for 3,000 screenshots; every feature is on every plan. Create a free ScreenshotNeo account.

FAQ

Can I export all of my Wachete history in one spreadsheet?

The documented selected-monitor UI export contains the last 100 values per monitor. The reviewed documentation does not confirm a UI export of every retained value.

Does Export monitored URLs include historical values?

No. It is documented as an account-wide URL inventory spreadsheet.

Does the API guarantee records older than my plan’s retention?

No such guarantee appears in the reviewed API or retention documentation. History retention depends on plan and is advertised as up to 12 months.

Is a last-checked timestamp the time a page changed?

No. Wachete distinguishes last checked from last changed.