Check an approved watch now
const url = 'http://localhost:11044/api/v1/realms/example/watches/example/check-now';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/watches/example/check-now \ --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'Runs as the signed-in owner and takes no body or query. DELIVERED means the host accepted the notification.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Name of the captured realm in the signed-in owner’s world that declares the watch
Name of one of that realm’s approved watches, which runs once now, as the owner, outside its schedule
Responses
Section titled “Responses”OK
What one owner-requested check of an approved Realm watch did. Answered by POST /realms/{realm}/watches/{watch}/check-now.
object
Notifications the host accepted in this run; they stay counted when later work fails or is refused
New items this run put in front of the judge, not counting items too big to judge
BASELINED (a first run: it recorded what the lens shows and delivered nothing), DELIVERED (at least one approved item was delivered), NOTHING_NEW, FAILED (the run stopped short; see problem), REFUSED (no such approved watch, the owner’s authority did not hold, or the run failed unexpectedly) or ALREADY_RUNNING (another run of this watch was in progress, so this one did nothing)
Why the run stopped short, such as LENS_FAILED, JUDGE_UNAVAILABLE or DELIVERY_FAILED; ITEM_TOO_BIG beside DELIVERED or NOTHING_NEW means one or more items were skipped as too big to judge. Null when nothing went wrong
Name of the watch that was checked; empty when the realm or watch name in the path is not a valid name

