Skip to main content
POST
Create a new request that will be sent to all active members of a loop for human review. The request supports multiple content types, response configurations, and notification systems.

Quick Start for Common Use Cases

Perfect for content moderation, document approval, or basic yes/no decisions.
Rate content quality, AI outputs, or customer service interactions.
Get written feedback, suggestions, or explanations from reviewers.
Identify multiple issues, features, or categories in content.
Send an AI-generated draft for a human to polish before delivery. Perfect for notifications, emails, or any message that benefits from a final human touch.

Authentication

string
required
Your API key for authentication

Path Parameters

string
required
The ID of the loop where the request will be created

Body Parameters

string
required
Processing urgency type
Options: time-sensitive, deferred
When processing_type is set to "time-sensitive", the timeout_seconds parameter becomes required. Time-sensitive requests must specify an explicit timeout.
string
required
Content type of the request
Options: markdown, image, file, video, audio
string
required
Priority level of the request
Options: low, medium, high, critical
string
required
The main content of the request (1-2000 characters)
string
URL of the image to review (required when type is image)
string[]
Array of image URLs for multi-image requests
string
URL of the document to review (required when type is file)
string
MIME type of the document, e.g. application/pdf (required when type is file)
string
Display name shown to reviewers (required when type is file)
string[]
Array of document URLs for multi-document requests
string[]
MIME types for each document in file_urls
string[]
Display names for each document in file_urls
string
URL of the video to review (required when type is video)
string[]
Array of video URLs for multi-video requests
string
URL of the audio to review (required when type is audio)
string[]
Array of audio URLs for multi-audio requests
object
Additional context data for the request (any valid JSON object)
integer
Timeout in seconds (60-86400)

Optional for: deferred requests (default: 30 days)
string
required
Type of response expected from reviewers
Options: text, editable_text, single_select, multi_select, rating, number
object
required
Configuration for the response type (varies by response_type)
Response Types Guide
required
Default response value if timeout occurs
string
required
Platform creating the request
Options: n8n, zapier, web_portal, api, mobile, webhook
string
Version of the platform used
string
URL to call when request is completed (webhook)

Response

boolean
Whether an error occurred
string
Success message
object

Response Type Quick Reference

For complete configuration options and advanced examples, visit the Response Types Guide.

Single Select - Choose One Option

Multi Select - Choose Multiple Options

Rating - Numeric Scale

Note: Only scale_max is required. Optional fields with defaults:
  • scale_min: defaults to 1
  • scale_step: defaults to 1
  • required: defaults to false

Number - Numeric Input

Note: Only max_value is required. Optional fields with defaults:
  • min_value: defaults to 1
  • decimal_places: defaults to 2
  • allow_negative: defaults to false
  • required: defaults to false

Text - Free Form Input

Need More Details?

Visit our complete Response Types Guide for advanced configurations, validation rules, and best practices.
Ready to test?
  1. Get your API key from app.hitl.sh
  2. Create a loop and copy the Loop ID
  3. Replace YOUR_API_KEY and YOUR_LOOP_ID in the examples below
  4. The request will be sent to all active members in your loop for review

Quick Test Examples

Copy any of these examples to test different response types:
Perfect for yes/no decisions or selecting one option.
cURL
For selecting multiple issues or features.
cURL
For quality ratings and scores.
cURL
For quantities, counts, or measurements.
cURL
For detailed feedback and explanations.
cURL
For AI-generated messages that need human review and revision before sending.
cURL

Use Cases

Content Moderation

Review flagged user-generated content:

Image Review

Review images for appropriate content:

Quality Rating

Rate AI-generated content quality:

Request Lifecycle

  1. Creation - Request is created and assigned a unique ID
  2. Broadcasting - Push notifications sent to all active loop members
  3. Pending - Waiting for a reviewer to respond
  4. Completed - Reviewer has submitted their response
  5. Webhook - Callback URL is notified (if configured)

Next Steps

Poll Request Status

Check the status and response of your request using the polling URL.

Set Up Webhooks

Configure webhooks to receive real-time notifications when requests complete.

Cancel Request

Cancel a pending request if it’s no longer needed.