patch · projects:write

Publish or unpublish

Unpublishing keeps the slug so old links can be turned back on.

Write

REST

patch/api/v1/projects/{id}/public
curl "https://herculeradar.com/api/v1/projects/:id/public" \
  --request PATCH \
  --header "Authorization: Bearer hr_live_…" \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: $(uuidgen)" \
  --data '{"enabled":"Acme"}'

MCP

Tool name set_public_dashboard. It takes the same input and returns the same { data, meta } envelope as REST, because both call the same function.

Publish or unpublish the public mentions page. Unpublishing keeps the slug.

Parameters

idrequiredstringProject id

Request body

{
  "type": "object",
  "required": [
    "enabled"
  ],
  "properties": {
    "enabled": {
      "type": "boolean"
    }
  }
}

Response

{
  "data": {
    "public_enabled": false,
    "url": null
  },
  "meta": {
    "capability": "set_public_dashboard",
    "requestId": "req_9f2b4a8c1d0e",
    "idempotencyReplayed": false,
    "docs": "https://herculeradar.com/docs/reference/set_public_dashboard"
  }
}

Authorization

Requires the projects:write scope. A credential without it gets 403 FORBIDDEN. Resources in projects the credential cannot reach answer 404 NOT_FOUND rather than 403, so ids cannot be probed across tenants.

Send an Idempotency-Key header. A completed response is replayed for 24 hours, so a retry after a timeout cannot create a duplicate.