Documentación para desarrolladores

Volver a comprobar un problema

POST/sites/{siteId}/issues/{issueId}/recheck
Permiso
issues:recheck
Herramienta MCP
recheck

Queue a recheck of an issue Reads every page the issue lists again, fresh (past page caches and CDNs); the issue is resolved only when the recheck no longer finds it. It also checks again the written changes of the issue's latest batch, so a not_live change that has appeared becomes applied.

Las descripciones vienen del documento OpenAPI y están en inglés.

Parámetros

NombreDóndeDetalles
siteIdObligatoriorutastringWebsite id, from GET /sites.
issueIdObligatoriorutastringIssue id, from GET /sites/{siteId}/issues or /actions.

Respuesta

200 · application/json

CampoDetalles
queuedtrue or false · required; Always true
crawlIdstring or null · required; Id of the recheck crawl
notestring · required; What happens next
linkstring · required; The issue in the app

Errores

EstadoSignificado
401Missing, unknown or revoked key. Codes: missing_key, invalid_key.
403The key lacks the scope, covers another website, or its owner lost access. Codes: missing_scope, other_site, owner_left, no_owner, forbidden.
404Not found. Codes: not_found.
409Conflict with the current state. Codes: already_queued.
422The request cannot be carried out. Codes: cannot_recheck.
429Too many requests this hour for this key. Codes: rate_limited.

Petición de ejemplo

curl -X POST \
  -H "Authorization: Bearer mr_ws_…" \
  "https://app.monoranks.com/api/v1/sites/SITE_ID/issues/ISSUE_ID/recheck"

Respuesta de ejemplo

{
  "queued": true,
  "crawlId": "e5a7c9e1-3f5b-4d7f-9b1d-5f7b9d1f3b5c",
  "note": "The issue is verified resolved only when this recheck no longer finds it.",
  "link": "https://app.monoranks.com/sites/3f6c2a1e-8b4d-4c7a-9e21-5d0b7a6f4c13/issues/b2e4c6a8-1d3f-4a5b-9c7d-0e2f4a6b8c1d"
}

El servidor MCP hace lo mismo con la herramienta recheck.