Request changes
POST/api/v1/review/{id}/request-changes
Send a card back to the agent with feedback. A revised version returns to the queue.
curl -X POST -H "Authorization: Bearer $REVNU_API_TOKEN" \
-H "content-type: application/json" \
-d '{"text":"Shorter, and lead with the case study."}' \
https://revnu.com/api/v1/review/k97…/request-changesBody
text, required, up to 8,000 UTF-8 bytes. The agent starts revising about 30 seconds later; the card sits in needs_revision until the new version comes back for review.
Responses
200 { ok: true }. 409 invalid_action if the card no longer accepts it.
Frequently Asked Questions
Does this send or publish anything?
No. The card goes back to Revnu in needs_revision and nothing ships. Revnu's revised version comes back as a card for you to review.
Which scope does this need?
review:write. A token without it gets 403 with requiredScope in the body. GET /me shows a token's scopes.
Are responses cached?
No. Every response is Cache-Control: no-store, so what you read is current.