v1Resources/Social Listening/patchCorrect a listening post
Correct a listening post
Overrides how a post was read: its sentiment, whether it is spam, or whether it is relevant. The post must have been analyzed already.
patch
listening:write/api/v1/listening/posts/{id}Query parameters
idstringrequired
The post's id, as returned by the listening posts reads.
Request body
clientIdstringrequired
The client (business) this concerns.
sentimentstring (positive | neutral | negative)optional
The corrected sentiment.
spambooleanoptional
True marks the post as spam.
relevantbooleanoptional
False marks the post as not relevant.
Response
dataobjectoptional
postobjectoptional
The post after the correction.
Errors
400The request is missing a required parameter or is otherwise malformed.
401Missing, invalid, expired, or revoked API key.
403The key lacks the required scope, or isn't authorized for this client/location.
404The resource wasn't found, or doesn't belong to your agency.
409The request conflicts with the current state of the resource — for example, changing the email or phone of a recipient who has already been messaged, or a team invite that was already accepted (or hasn't been accepted yet).
429Too many requests. Retry after the number of seconds in the Retry-After header.
patch/api/v1/listening/posts/{id}
Your API key
id *
Request body*
{}