Developers

SitemapDiff API

Manage daily sitemap monitors, read check and change history, and configure notifications. Manual run-now checks are intentionally not available.

Authentication

Create a key under Account settings, then send it in the x-api-key header. The complete key is shown only once.

curl https://sitemapdiff.com/api/v1/monitors \
  -H "x-api-key: sd_live_..."

MCP server

Connect a Streamable HTTP MCP client to https://sitemapdiff.com/mcp and send the same key as a Bearer token.

Authorization: Bearer sd_live_...

REST v1

Endpoints

OpenAPI 3.1

GET/api/v1/accountAccount, plan, usage and limits

GET · POST/api/v1/monitorsList or create daily monitors

GET · PATCH · DELETE/api/v1/monitors/{id}Inspect, pause, resume or delete

GET/api/v1/monitors/{id}/check-runsScheduled check history

GET/api/v1/monitors/{id}/check-runs/{runId}One exact check run

GET/api/v1/monitors/{id}/changesPaginated change history; include URL arrays on request

GET/api/v1/monitors/{id}/changes/latestLatest change with complete added and removed URLs

GET/api/v1/monitors/{id}/changes/{changeId}Added and removed URLs

GET · PATCH/api/v1/account/notificationsAccount notification defaults

GET · PATCH/api/v1/monitors/{id}/notificationsMonitor override or inheritance

POST/api/v1/account/notifications/testSend a test webhook

Change details

Get the URLs that changed

The standard changes collection stays compact for fast pagination. Use the latest endpoint for the newest complete change, or opt into URL arrays across a paginated page with include=urls.

Latest detailed change

Returns the newest change for one monitor with complete addedUrls and removedUrls arrays.

curl "https://sitemapdiff.com/api/v1/monitors/{id}/changes/latest" \
  -H "x-api-key: sd_live_..."

Detailed change history

Adds both URL arrays to every item while preserving the normal limit, cursor, and nextCursor behavior.

curl "https://sitemapdiff.com/api/v1/monitors/{id}/changes?include=urls&limit=20" \
  -H "x-api-key: sd_live_..."

Pagination

List endpoints accept limit from 1–100 and an opaque cursor. Responses include nextCursor when another page exists.

Errors and limits

Errors include a stable code, message and request ID. Rate-limited requests return HTTP 429.