Authorization
Your Narada API key for authentication. Must be the same key used to create
the original task.
Path Parameters
The unique identifier returned from the Remote Dispatch
API when the task was created.
Response
Current status of the automation task. Possible values: -
"pending"
- Task
is still running - "success"
- Task completed successfully - "error"
-
Task failed with an errorTask response data.
null
when status is "pending"
.ISO 8601 timestamp when the task was initially created.
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:Webhooks (Recommended)
Receive real-time notifications when tasks complete. More efficient and scalable than polling.
Polling Implementation
Complete polling implementation examples with error handling and best practices.
Rate Limiting: Implement reasonable polling intervals (5-10 seconds) to
avoid overwhelming the API. Use exponential backoff for production
applications.
Comparison: Polling vs Webhooks
Feature | Polling | Webhooks |
---|---|---|
Setup Complexity | Low | Medium |
Real-time Updates | No (delayed by interval) | Yes |
Resource Usage | Higher (active requests) | Lower |
Reliability | Medium | High (with retries) |
Firewall Friendly | Yes | Requires open ports |