Publish the shortlist to the client
Publish the live shortlist as a new version the client’s portal shows. It reaches the client, so it runs only from a proposal: preview_action, show the person, then apply_proposal once they agree. Calling this route directly is refused with proposal_required, and nothing is published. The version freezes who is on the shortlist when the proposal is applied, best first, with each person’s name, title, company, place, LinkedIn address and why they are on it (a qualified match, or selected by the recruiter); never notes, scores’ workings or removal reasons. Publishing a shortlist that hasn’t changed returns the version already published. Send expected_members (how many people the person was shown, get_project’s shortlisted) and a shortlist that has moved since is refused with shortlist_changed. Does not use credits. It reaches the client, so the MCP server asks the person first, showing who gets what.
Needs scope shortlists:write.
Authorizations
An API key from Settings → Usage → API (rvc_live_…).
Path Parameters
A project id
Body
How many people the person was shown; refused if the shortlist holds a different number now.
x >= 0