Skip to main content
GET
Get asynchronous command
When you send a command with async: true, the API responds immediately with a commandId and runs the command in the background. This endpoint tells you what happened to it.

Status

status is not the command’s success. A command that ran and failed (invalid number, disconnected session) ends up completed with result.success: false and the reason in result.error. status: "failed" only covers worker failure.
The result field carries the same payload as the command.result webhook and is only filled in when the command finishes. Until then it is null.

Scope and retention

You can only see commands from your own sessions. An API Key restricted to a session can only query that session’s commands. A third party’s command returns 404, just like a nonexistent commandId.
The result is available for a limited window — about 1 hour after execution (24 hours in case of worker failure). After that, the response is 404. For guaranteed delivery, use the command.result webhook instead of polling.

Authorizations

Authorization
string
header
required

API Key for authentication. Format: <API_KEY>

Path Parameters

commandId
string
required
Minimum string length: 1

Response

Successful response