community

Set Digest Lead

Set as top story / Clear breaking (Digest Design PRD §2.2).

Rewrites payload_json and re-renders. NO RE-RUN: the model already answered, the contract already accepted what it said, and asking it again to move a rule three inches would spend a call to get a different digest.

What this can change is which item leads and whether the badge shows. What it cannot change is a single word on the card. That split is the whole design of the endpoint: every string in the payload arrived through digest_contract.validate_payload and the house-style gate at the write path, and an override that accepted text would be a member-facing route that writes unvalidated prose onto a post signed by the platform.

Clearing the badge is urgent: false, and it is allowed on any lead. SETTING it is not offered here at all -- urgent is earned by one of four same-day events that only the compose pass can see, and a button that granted it would turn a rule into a preference.

post/api/community/admin/messages/{message_id}/digest-lead

Request

  • Base URL
    https://app.archangelhealth.ai (the document declares no server; this is the origin it was published from)
  • URL
    https://app.archangelhealth.ai/api/community/admin/messages/{message_id}/digest-lead
  • Auth
    none declared

Path parameters

message_idinteger required

Headers

authorizationstring nullable

Request body

urlstring nullable
urgentboolean nullable

Response

Successful Response

unknown required

Changes

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