curl -X POST 'https://api.narada.ai/fast/v2/remote-dispatch' \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: YOUR_API_KEY' \
  -d '{
    "prompt": "/Operator click on Insurance header",
    "sessionId": "your-session-id",
    "clearChat": true
  }'

{
  "requestId": "req_abc123def456"
}

curl -X POST 'https://api.narada.ai/fast/v2/remote-dispatch' \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: YOUR_API_KEY' \
  -d '{
    "prompt": "/Operator click on Insurance header",
    "sessionId": "your-session-id",
    "clearChat": true
  }'

{
  "requestId": "req_abc123def456"
}

The Remote Dispatch API allows you to execute automation tasks remotely on browser sessions with the Narada Chrome Extension installed. This endpoint returns immediately with a request ID for tracking, while the actual automation runs asynchronously.

​
Authorization

​
x-api-key
string
required

Your Narada API key for authentication. Contact support to obtain your API key.

​
Content-Type
string
required

Must be set to application/json.

​
Body

​
prompt
string
required

The natural language instruction for the task to execute. Must be prefixed with /Operator to invoke the web agent.

​
sessionId
string

Unique identifier for the specific browser window to target. Please see authentication for more information.

​
clearChat
boolean
default:"false"

Whether to clear the chat history before executing the command. Recommended for isolated tasks.

​
saveScreenshots
boolean
default:"false"

Whether to capture screenshots during the automation process. When enabled, screenshots are automatically saved as an animated GIF to your local Narada Downloads directory. Learn more about screenshot capture.

​
responseFormat
object

Specify structured output format using JSON Schema. See JSON Schema documentation for detailed examples.

​
callbackUrl
string

Optional webhook URL to receive the response asynchronously. Recommended for long-running tasks. See Webhooks documentation.

​
Response

​
requestId
string
required

Unique identifier for tracking the request. Use this ID for: - Polling the status via GET /responses/ - Correlating webhook responses - Debug and monitoring purposes

The API returns 202 ACCEPTED immediately while the automation task runs in the background. Use the requestId to track progress through polling or webhooks.

​
Example Commands

# Simple navigation
/Operator navigate to the reports section

# Data extraction
/Operator extract customer information from the current table

# Multi-step workflow
/Operator 1) Navigate to customer database, 2) Search overdue accounts, 3) Export to CSV

# Conditional logic
/Operator if error messages exist, screenshot them, otherwise extract user count

​
Best Practices

Command Prefix: Always prefix automation commands with /Operator to invoke the web agent. Commands without this prefix will not be processed.

Descriptive Prompts: Be specific about your intentions. Instead of /Operator click button, use /Operator click the Submit button in the contact form.

  • Use session IDs to target specific browser contexts when working with multiple windows
  • Implement timeouts for long-running automation tasks
  • Use webhooks for better performance with asynchronous processing
  • Test with simple commands before implementing complex workflows
  • Enable screenshots for debugging complex automation sequences

​
Rate Limiting

API requests are subject to rate limiting based on your subscription plan. For high-volume usage or custom rate limits, contact support@narada.ai.

​
Next Steps