Optimizations

Get Content Guard monitoring status

Content Guard monitoring state for one article. hasPublishedUrl is a RECOVERABILITY judgment, not a presence test on the stored URL: the server runs the same recovery ladder arming runs — the stored URL when absolute; otherwise (empty slot, non-FraseCMS) the newest live CMS-inventory URL; otherwise, for a FraseCMS article with a live published post, an address re-derived from the site's CURRENT settings. So a stored relative path ("/blog/post", which a FraseCMS publish produces before domain setup) reports hasPublishedUrl: true once domain setup is finished — no re-publish needed — and false means the enable WOULD be rejected right now. publishedUrlIssue names the residual after recovery failed: "missing" (no stored URL and nothing recoverable) or "not_absolute" (a stored path that could not be re-derived — for FraseCMS that can mean domain setup unfinished, the post not live, or FraseCMS disabled for the site). Read the pair together rather than testing the URL yourself: this is exactly the condition enabling enforces.

get/content/{id}/monitoring

Request

  • Base URL: https://next.frase.io/api/v1
  • URL: https://next.frase.io/api/v1/content/{id}/monitoring
  • Auth: one of:
    • API key in header X-API-KEY
    • HTTP bearer

Path parameters

idstring uuid required

Content ID.

Response

Monitoring status

Changes

No recorded changes to this operation across all 1 revision of this API.