Inspect action authorization or revoke trading permission
get_deployment_action_statusReturns the status of a pending or completed deployment authorization request created by start_deployment, stop_deployment, update_deployment_revision, run_deployment_once, or place_trade. Includes the active, expired or revoked trading window when present. Omit operation or use status for reads. Use operation=revoke_trade_window with the source actionId to revoke further-trade authority; requires place_trade scope. Revocation is idempotent and prevents new claims, but does not cancel submitted or in-flight orders, stop bots or alter other accounts. Use this after the user approves or denies the website authorization URL. Copy the actual actionId returned by the action tool; never guess an authorization request id. A deploymentId, botId or revisionId is not an actionId. If no action request has been created or returned, prepare the requested action first. Do not poll a known unapproved request merely to confirm that approval is still pending. For run_deployment_once, the authorization status describes approval and dispatch, not the strategy iteration. Pending approval means no strategy iteration has started. A completed action with metadata.executionResult.status=launched means launch accepted; completion and trades remain unverified. A skipped result started no new iteration. An already_recorded result is a duplicate dispatch; inspect its run_id, last_run_status and run history. A failed or unconfirmed dispatch without terminal run evidence leaves the iteration outcome unknown. Inspect run history before any new request; do not automatically retry or infer that the run failed or finished. A balance or holdings report does not verify iteration completion. Answer questions about whether the RUN finished from iteration evidence: launched means completion is unverified. Do not lead with Yes and then qualify it when only the approval completed or launch was accepted.For Codex, Claude, Cursor, and other clients without BotSpot native confirmation cards, return the exact authorizationUrl as a clickable Markdown link in your reply. Do not say a card or button was created unless the client actually rendered it. BotSpot clients may render structuredContent as a native confirmation, but a button name alone is not an approval link. A pending request is not execution; only the signed-in user may approve on the website. Report expiry and check get_deployment_action_status after approval.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"actionId": "<actionId>"
},
"name": "get_deployment_action_status"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| actionId | Yes | ||
| operation | No | Omit for status. revoke_trade_window revokes further trades authorized by this source action; requires place_trade scope and does not cancel submitted orders. |