Operation Type (for Signing)
Request Body
| Field | Type | Need | Description | Example |
|---|---|---|---|---|
”account” | string | required | User’s wallet address | 42trU9A5… |
“signature” | string | required | Cryptographic signature | 5j1Vy9Uq… |
“timestamp” | integer | required | Current timestamp in milliseconds | 1716200000000 |
”strategy_type” | string | required | Strategy type. See Strategy parameters | conditional |
”params” | object | required | Parameters for the strategy type. See Strategy parameters | See below |
”scheduled_start_at” | integer | optional | Start time in milliseconds. Until then, the strategy is pending | 1716203600000 |
”scheduled_end_at” | integer | optional | End time in milliseconds. Must be after scheduled_start_at. At this time the strategy expires | 1716207200000 |
”expires_at” | integer | optional | Expiry time in milliseconds. At this time the strategy expires | 1716207200000 |
”agent_wallet” | string | optional | Agent wallet address | 69trU9A5… |
“expiry_window” | integer | optional | Signature expiry in milliseconds | 30000 |
Signing
Signstrategy_type, params, and any schedule fields as the data object, like any other request. See Signing. Keys inside params are sorted too. For the request above, the message to sign is:
Response
- Status 200: Strategy created
- Status 400: Invalid parameters, or the account cannot run the strategy. The
errorfield says why, for exampleinvalid strategy definition: clip count must be between 2 and 100orSTRATEGIST_INSUFFICIENT_BALANCE
- Status 429: The account already has 100 strategies that have not finished (
STRATEGIST_ORDER_STRATEGY_LIMIT_REACHED), or the rate limit is exceeded - Status 500: Internal server error
- Status 503: The strategy service is not ready. Retry later
error values with status 400: