Control specific betting account

POST /bookieaccount/control/{id}/

Operation ID: send_command_to_bot

Send a command to the bot for a specific bookie account. This endpoint allows you to control individual account bots.

Path Parameters

Parameter	Type	Required	Description
id	string	Yes	Account ID of the bookie account to control

Request Body

{
  "command": "ON"
}

Parameters

Field	Type	Required	Description
command	string	Yes	Command name. Available commands: ON, OFF

Available Commands

Command	Description
ON	Turn on the bot for this specific account
OFF	Turn off the bot for this specific account

Response

Success Response (200)

{
  "status": "success",
  "message": "Bot turned ON successfully",
  "account_id": "123",
  "display_name": "TAB Main Account",
  "bot_status": "RUNNING",
  "timestamp": "2024-01-24T21:00:00+11:00",
  "previous_status": "STOPPED",
  "session_info": {
    "active_sessions": 1,
    "session_start_time": "2024-01-24T21:00:00+11:00"
  }
}

Error Responses

• 400 Bad Request - Invalid command or request format

• 401 Invalid credentials - Authentication token is invalid or missing

• 404 Not Found - Account with specified ID not found

• 406 Invalid bot - Bot is invalid or cannot be controlled

• 500 Internal server error - Server encountered an error processing the request

Usage

Turn on specific bot:

curl -X POST "https://betmatic.app/api/bookieaccount/control/123/" \
  -H "Content-Type: application/json" \
  -H "Authorization: Token your_token" \
  -d '{
    "command": "ON"
  }'

Turn off specific bot:

curl -X POST "https://betmatic.app/api/bookieaccount/control/123/" \
  -H "Content-Type: application/json" \
  -H "Authorization: Token your_token" \
  -d '{
    "command": "OFF"
  }'

Potential Use Cases

1. Selective Control: Control individual accounts without affecting others

2. Troubleshooting: Turn off problematic accounts while keeping others running

3. Account Maintenance: Temporarily disable specific accounts for maintenance

4. Performance Optimization: Control accounts based on individual performance

5. Risk Management: Disable high-risk accounts while maintaining others

6. Testing: Test individual account functionality without system-wide impact

7. Load Balancing: Distribute load by selectively enabling/disabling accounts

8. Compliance: Disable specific accounts that may have compliance issues

Authentication

This endpoint requires authentication. Include your token in the Authorization header:

Authorization: Token your_token_here

Important Notes

• Individual Control: This command affects only the specified account

• Immediate Effect: Commands take effect immediately for the target account

• Status Tracking: The response includes current and previous bot status

• Session Management: Bot status changes affect active sessions

• Error Handling: Specific error codes help identify issues with individual accounts

• Account Validation: The system validates account ownership before executing commands

Best Practices

1. Verify Account ID: Ensure you're controlling the correct account

2. Monitor Status: Check the response to confirm the command was executed successfully

3. Consider Dependencies: Be aware of any betting strategies that depend on this account

4. Gradual Changes: Make incremental changes rather than bulk operations when possible

5. Documentation: Keep records of manual bot control actions for audit purposes

Error Code Details

• 406 Invalid bot: The bot associated with this account cannot be controlled, possibly due to:

  • Bot is not properly configured

  • Bot is in maintenance mode

  • Account has technical issues

  • Bot service is unavailable