Documentation
PingMyThing documentation
Start with the task you are trying to complete.
The docs cover sending selected results, using starter or custom checks, deploying through tools you already use, reading results, separating projects and handling credentials.
New to PMT? Start with How PMT Works, then send one real result.
New to PMT?
1. Understand the result path
Source → PMT → view or use the result.
2. Send one result
Use a starter check or your own source logic.
3. Add structure only when needed
Projects, deployment and token lifecycle come after first value.
Send something to PMT
These pages take you from the basic model to a real submitted result.
HOW PMT WORKS
Understand the source → PMT → view/use model, what accepted means, and what PMT deliberately does not do.
SIGNAL FORMAT & EXAMPLES
The exact send fields, descriptive sens, numeric val, GET and JSON POST examples.
STARTER CHECKS / YOUR OWN CHECKS
Use one of the two source routes: a transparent PMT starter check where it fits, or your own script, job, application, website, gateway or device.
Deploy checks and use the results
PMT collects the answer. Existing tools can deploy the check. The webapp is the normal human view; API/CLI access is there when you need to manipulate or integrate the data.
GROUP POLICY DEPLOYMENT
Deploy transparent PowerShell checks through Group Policy, including persistent WATCH and temporary ASK patterns.
WEBAPP
See selected results, expected absence, recent history and presentation rules in the normal human-facing view.
API / CLI ACCESS
Query authorised stored results from PowerShell or another application, filter them, use latest/history modes and export when needed.
Separate access and protect the result path
Keep customers, operational subjects and credentials bounded to the purpose they actually serve.
PROJECT SEPARATION
Use projects and scoped access to separate customers or operational subjects while combining authorised views where required.
TOKEN STORAGE & ROTATION
Store send/read credentials deliberately, rotate or revoke them, protect browser exports, and account for current egress cache behaviour when access changes.
KEEP PMT DATA MINIMAL
Avoid secrets, personal records, unnecessary raw logs and broad telemetry. Send the selected operational result instead.
Documentation should stay narrower than the product story.
The commercial pages explain why PMT may fit.
These docs explain how to use the result path accurately.
If a technical page needs the entire PMT proposition repeated before it can explain the task, the documentation is doing too much.
Need the product boundary?
Use Trust & Security for the security model and About for the product philosophy.
Use the technical pages above for implementation.