curl -X GET 'https://api.narada.ai/fast/v2/remote-dispatch/responses/req_abc123def456' \
  -H 'x-api-key: YOUR_API_KEY'
{
  "status": "pending",
  "response": null,
  "createdAt": "2024-12-19T00:00:00.000000+00:00",
  "completedAt": null
}
curl -X GET 'https://api.narada.ai/fast/v2/remote-dispatch/responses/req_abc123def456' \
  -H 'x-api-key: YOUR_API_KEY'
{
  "status": "pending",
  "response": null,
  "createdAt": "2024-12-19T00:00:00.000000+00:00",
  "completedAt": null
}

Use this endpoint to poll for the completion status and results of a previously submitted automation task. This is an alternative to using webhooks for receiving task results.

Authorization

x-api-key
string
required

Your Narada API key for authentication. Must be the same key used to create the original task.

Path Parameters

requestId
string
required

The unique identifier returned from the Remote Dispatch API when the task was created.

Response

status
string
required

Current status of the automation task. Possible values: - "pending" - Task is still running - "success" - Task completed successfully - "error" - Task failed with an error

response
object | null

Task response data. null when status is "pending".

createdAt
string
required

ISO 8601 timestamp when the task was initially created.

completedAt
string | null

ISO 8601 timestamp when the task completed. null if still pending.

Response Handling Options

This endpoint provides synchronous access to task results. For production applications, consider these alternatives:

Rate Limiting: Implement reasonable polling intervals (5-10 seconds) to avoid overwhelming the API. Use exponential backoff for production applications.

Comparison: Polling vs Webhooks

FeaturePollingWebhooks
Setup ComplexityLowMedium
Real-time UpdatesNo (delayed by interval)Yes
Resource UsageHigher (active requests)Lower
ReliabilityMediumHigh (with retries)
Firewall FriendlyYesRequires open ports

Next Steps