PATCH https://api.cryptohopper.com/v1/hopper/{id}

Updates the name and enabled state of the hopper and merges the config keys you send into its config. Returns the result with API keys masked.

OAuth scope: manage About scopes

Always send name and enabled: a missing name renames the hopper to "Unnamed bot", and a missing enabled (or any value other than 1) disables it. The api_config object in the request model is not read; put keys in config instead.

Example request

curl -X PATCH "https://api.cryptohopper.com/v1/hopper/HOPPER_ID" \
  -H "access-token: YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name":"My BTC bot","enabled":1,"config":{"max_open_positions":10,"stop_loss":1,"stop_loss_percentage":5}}'

Parameters

Headers

NameTypeRequiredDescription
access-token string Required The OAuth access token of the user.

Path parameters

NameTypeRequiredDescription
id string Required Hopper ID.

Request body

JSON, model HopperIdPATCH

FieldTypeRequiredDescription
namestringOptional
enabledintegerOptional
api_configobjectOptional
api_keystringOptional
api_secretstringOptional
kraken_extra_keystringOptional
kraken_private_extra_keystringOptional
gdax_api_passphrasestringOptional
gdax_post_onlystringOptional

Response

Example response (illustrative values)

{
    "data": {
        "status": 1,
        "message": "Bot has been updated.",
        "name": "My BTC bot",
        "enabled": "1",
        "config": {
            "name": "My BTC bot",
            "exchange": "binance",
            "collect_currency": "usdt",
            "api_key": "***",
            "api_secret": "***",
            "max_open_positions": 10,
            "stop_loss": 1,
            "stop_loss_percentage": 5
        }
    }
}

Status codes: 200. Errors return JSON with status, error and message. See How the API works for response codes and rate limits.