Reject Nodes from Moderation

/services/v2/node/{node}/reject

The purpose of this API is to reject content from the moderation queue. When content is rejected, it will no longer be in the standard moderation queue and remains unpublished . Rejected nodes in moderation may be retrieved using the Retrieve nodes in moderation GET call with the rejected queue type parameter. Nodes may be sent back to moderation by using the send a node to moderation PUT.
https://developer.devada.com/reference#send-a-node-to-moderation

🚧

Permissions & Notes:

  • You must have the permission called View Nodes in Moderation under Moderation Roles and the Reject_Moderated permission to make this API call.

This functionality was added in the 2.19.0 Release

Sample Request

"https://apidocs.cloud.answerhub.com/services/v2/node/23/reject"

-u answerhub:test123
-H "Accept: application/json"
-H "Content-type: application/json"
-X PUT "https://apidocs.cloud.answerhub.com/services/v2/node/23/reject"

Sample Response

HTTP Error Response codes:

Success Response:

  • 200: Message: Node: {0} has been successfully rejected

Error Responses:

  • 403: Role / Permission issue “REJECT_MODERATED” revoked role.

Message: We're sorry, but you are not allowed to reject {0} in moderation.

  • 403: Permission -Node not being in moderation and/or reported queues.

Message: We're sorry, but you cannot reject the node.

  • 404: Not found – Node not found; Message : Node not found
Language
Authentication
Basic
base64
:
Click Try It! to start a request and see the response here!