REST API
Code / SDK
One authenticated POST from anything that speaks HTTP.
In plain English
LoopQuest is a place where a person quickly checks the work an AI or automation has done. Connecting REST API means that whenever REST API produces something that should be looked at by a human, it sends that item to LoopQuest. Someone on your team reviews it in a few seconds, and their decision is sent straight back to REST API so the rest of your process can carry on, with a real person accountable for the call.
When you'd use it
No SDK, no platform — just a backend, a cron job or a shell script. POST your output to one endpoint, poll or receive a webhook, done. This is the layer every other integration is built on.
What you'll need
- A free LoopQuest account. Sign up if you don't have one.
- A project and its API key — find it under Workspaces → your project → API keys. The key is how REST API proves it's allowed to send you work.
- An account on REST API itself, with the workflow or agent you want to add a human check to.
How to set it up
- 1Get a project API key from Workspaces → your project → API keys.
- 2POST your output to /api/v1/tasks with an Authorization: Bearer header.
- 3Optionally send an Idempotency-Key so retries don't duplicate.
- 4Receive the signed verdict at your callback_url, or GET /api/v1/tasks/{id} to poll.
Copy-paste starting point:
curl -X POST https://loopquest.tomphillips.uk/api/v1/tasks \
-H "authorization: Bearer $LOOPQUEST_KEY" \
-H "content-type: application/json" \
-d '{
"module": "swiper",
"payload": { "ticket": 4821, "predicted": "auto-approve" },
"callback_url": "https://your-app.com/loopquest/verdict"
}'Recipes: gate or monitor
Two ways to put a human in the loop with REST API. A gate blocks until someone approves; a monitor reviews in the background without slowing anything down.
Gate — block until approved
With REST API you control the call, so you await the verdict directly before doing anything consequential.
- 1POST the output to /api/v1/tasks with a mode of "gate" and a timeout_seconds.
- 2Poll GET /api/v1/tasks/{id} until the status is no longer "pending", or receive the signed webhook.
- 3Continue on an approve, halt on a reject. If it times out, it resolves fail-closed on its own.
- 4Verify the X-LoopQuest-Signature on any webhook before trusting it.
Monitor — review without blocking
Monitor mode never holds REST API up. The flow proceeds immediately and LoopQuest reviews a copy for quality.
- 1Send the output with a mode of "monitor" and don't wait on the result.
- 2REST API carries straight on, nothing is blocked.
- 3Verdicts are logged and scored over time. Sample a fraction for QA, or review every item.
What happens after a review
The moment a reviewer decides, LoopQuest sends the result back to the web address you gave it (your callback_url). The message says what was decided, whether it was approved, flagged, which option was picked, or the corrected values, so your automation can act on it automatically.
For developers: each callback is signed with an X-LoopQuest-Signature HMAC header. Verify it before trusting the payload. Full details are in the API reference.
Pairs well with
The review games that best fit the kind of output REST API tends to produce.