Update a news article.
Changed onUpdate an engagement news article. Any pending (not yet sent) deliveries for this engagement are discarded and re-queued from the updated document. While an engagement is live, its audience, targeting and scheduling fields cannot be changed (for fixed frequency engagements neither can its content); pause it first or the request fails with 409. Setting status to live starts delivery. type, project, organisation and createdBy are set server-side and ignored if supplied. searchContent is derived from subject (recomputed only when subject is sent) and ignored if supplied. News items always use a dynamic audience, so frequencyType: "fixed" and csvContacts are ignored unless the item already stores them.
Request
- Base URLhttps://api.gleap.io/v3
- URLhttps://api.gleap.io/v3/engagement/news/{newsId}
- AuthHTTP bearer
Path parameters
Headers
Request body
Response
Ok
Changes
- info
removed
subschema #1subschema #3from the response bodyallOflist for the response status
- info
- info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status
- info