Pull upcoming-job footprints plus full order/client/agent detail from Inspection Support Network (ISN) beyond the basic schedule+report connect
domain: inspectionsupport.net · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
If you don't already know the customer's ISN Company Key and Service Domain, request an integration username/password from ISN (sys@inspectionsupport.net) to call the Admin API documented at http://api.isnadmin.com
GET the Admin API's isn/url endpoint with the company key to resolve the client's Service Domain (e.g. 4isn.com); skip this step entirely if you already know the domain
Construct the tenant REST endpoint as {service_domain}/{company_key}/rest, documented at http://api.inspectionsupport.net/, and authenticate with an Access Key/Secret Access Key pair (preferred over raw username/password)
Call GET /orders/footprints to retrieve stub records for the inspector's upcoming inspections
For each footprint, call GET /order/{id}, /client/{id}, and /agent/{id} to hydrate full order, client, and agent detail
After processing a footprint, call its DELETE endpoint — ISN only auto-purges unclaimed footprints after a customer-configurable retention window
Known gotchas
ISN maintains two separate REST APIs (isnadmin.com Admin API vs. the per-tenant API) — using the Admin API when you already know the Service Domain is an unnecessary extra hop
Footprints are one-time consumption stubs, not the system of record; failing to delete them after reading risks duplicate downstream processing
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?