Accept or reject a retained proposal
const url = 'http://localhost:11044/api/v1/realms/example/proposals/example/decision';const options = {method: 'POST', headers: {'X-Embabel-Api-Key': '<X-Embabel-Api-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url http://localhost:11044/api/v1/realms/example/proposals/example/decision \ --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'Current owner authority is required. UNKNOWN is not proof that no effect occurred.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Name of the admitted realm the proposal came from, in the signed-in owner’s own world
Id of a pending proposal, as the list route returns it: a canonical lower-case UUID. Any other form answers 400 REFUSED; one that is not pending under this realm, or was claimed by another decision first, answers 409 CONFLICT
Responses
Section titled “Responses”OK
How an owner’s accept or reject of a realm write proposal ended, as POST /realms/{realm}/proposals/{proposalId}/decision answers it, a refused or failed request included
object
APPLIED (accepted and written, 200), REJECTED (taken out of the mailbox, 200), REFUSED (bad request, or the proposal no longer applies, 400), CONFLICT (no longer pending, or decided concurrently, 409), or UNKNOWN (503: the write may or may not have landed)

