> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ninjatrader.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ninjatrader.com/_mcp/server.

# Modify Alert

POST https://demo.tradovateapi.com/v1/alert/modifyalert
Content-Type: application/json

### Modify an existing alert and re-arm it.

**Available to:** All authenticated users

**Environments:** Demo, Live

**[Rate Limit](/api/authentication#request-rate-limits-and-time-penalties):** No endpoint-specific limit

Updates an existing `Alert` identified by `alertId`. The alert must belong to the calling user. The server re-parses the supplied `expression` before applying changes; on success it replaces the alert's `expression`, `validUntil`, `triggerLimits`, and `message`, resets the `triggeredCounter` and clears any `failure`, sets `status` back to `Active`, and resumes watching the condition. The response returns the updated `alert`.

Request fields:

- `alertId` (required) — the `id` of the alert to modify, from [`createAlert`](/api/rest-api-endpoints/alerts/create-alert) or [`alertItem`](/api/rest-api-endpoints/alerts/alert-item).
- `expression` (required) — the new condition, up to 4096 characters.
- `validUntil` — optional new expiration time.
- `triggerLimits` — optional new trigger limit (0–10).
- `message` — optional new message text (up to 256 characters).

Because a modify resets the trigger counter and reactivates the alert, it is equivalent to a [`resetAlert`](/api/rest-api-endpoints/alerts/reset-alert) that also changes the alert's parameters. If the new `expression` fails to parse, the existing alert is left unchanged and the response carries a non-empty `errorText`. If the parse succeeds but the update cannot be persisted, the server resumes watching the original alert and returns an `errorText` beginning with `"Cannot apply changes:"`.

**Common Failure Scenarios**

- The new `expression` is malformed or references an unsupported condition.
- `alertId` does not exist or is not owned by the calling user.

**Error Messages**

| `errorText` | Trigger |
|-------------|---------|
| `"Cannot apply changes: ..."` | The `expression` parsed, but the update could not be saved; the original alert continues watching. |
| Non-empty `errorText` | The request failed; the field describes the reason (most commonly an `expression` that could not be parsed). |

Reference: https://docs.ninjatrader.com/api/rest-api-endpoints/alerts/modify-alert

## OpenAPI Specification

```yaml
openapi: 3.1.0
info:
  title: public
  version: 1.0.0
paths:
  /alert/modifyalert:
    post:
      operationId: modifyAlert
      summary: Modify Alert
      description: >-
        ### Modify an existing alert and re-arm it.


        **Available to:** All authenticated users


        **Environments:** Demo, Live


        **[Rate
        Limit](/api/authentication#request-rate-limits-and-time-penalties):** No
        endpoint-specific limit


        Updates an existing `Alert` identified by `alertId`. The alert must
        belong to the calling user. The server re-parses the supplied
        `expression` before applying changes; on success it replaces the alert's
        `expression`, `validUntil`, `triggerLimits`, and `message`, resets the
        `triggeredCounter` and clears any `failure`, sets `status` back to
        `Active`, and resumes watching the condition. The response returns the
        updated `alert`.


        Request fields:


        - `alertId` (required) — the `id` of the alert to modify, from
        [`createAlert`](/api/rest-api-endpoints/alerts/create-alert) or
        [`alertItem`](/api/rest-api-endpoints/alerts/alert-item).

        - `expression` (required) — the new condition, up to 4096 characters.

        - `validUntil` — optional new expiration time.

        - `triggerLimits` — optional new trigger limit (0–10).

        - `message` — optional new message text (up to 256 characters).


        Because a modify resets the trigger counter and reactivates the alert,
        it is equivalent to a
        [`resetAlert`](/api/rest-api-endpoints/alerts/reset-alert) that also
        changes the alert's parameters. If the new `expression` fails to parse,
        the existing alert is left unchanged and the response carries a
        non-empty `errorText`. If the parse succeeds but the update cannot be
        persisted, the server resumes watching the original alert and returns an
        `errorText` beginning with `"Cannot apply changes:"`.


        **Common Failure Scenarios**


        - The new `expression` is malformed or references an unsupported
        condition.

        - `alertId` does not exist or is not owned by the calling user.


        **Error Messages**


        | `errorText` | Trigger |

        |-------------|---------|

        | `"Cannot apply changes: ..."` | The `expression` parsed, but the
        update could not be saved; the original alert continues watching. |

        | Non-empty `errorText` | The request failed; the field describes the
        reason (most commonly an `expression` that could not be parsed). |
      tags:
        - Alerts
      parameters:
        - name: Authorization
          in: header
          description: Bearer authentication
          required: true
          schema:
            type: string
      responses:
        '200':
          description: AlertResponse
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AlertResponse'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ModifyAlert'
servers:
  - url: https://demo.tradovateapi.com/v1
    description: Demo
  - url: https://live.tradovateapi.com/v1
    description: Live
components:
  schemas:
    ModifyAlert:
      type: object
      properties:
        alertId:
          type: integer
          format: int64
        expression:
          type: string
        validUntil:
          type: string
          format: date-time
        triggerLimits:
          type: integer
        message:
          type: string
      required:
        - alertId
        - expression
      title: ModifyAlert
    AlertStatus:
      type: string
      enum:
        - Active
        - Expired
        - Failed
        - Inactive
        - TriggeredOut
      description: Active, Expired, Failed, Inactive, TriggeredOut
      title: AlertStatus
    Alert:
      type: object
      properties:
        id:
          type: integer
          format: int64
        timestamp:
          type: string
          format: date-time
        userId:
          type: integer
          format: int64
        status:
          $ref: '#/components/schemas/AlertStatus'
          description: Active, Expired, Failed, Inactive, TriggeredOut
        expression:
          type: string
        validUntil:
          type: string
          format: date-time
        triggerLimits:
          type: integer
        triggeredCounter:
          type: integer
        failure:
          type: string
        message:
          type: string
      required:
        - timestamp
        - userId
        - status
        - expression
      title: Alert
    AlertResponse:
      type: object
      properties:
        errorText:
          type: string
          description: Non-empty if the request failed
        alert:
          $ref: '#/components/schemas/Alert'
      title: AlertResponse
  securitySchemes:
    bearer_access_token:
      type: http
      scheme: bearer

```

## Examples



**Request**

```json
{
  "alertId": 1,
  "expression": "string"
}
```

**Response**

```json
{
  "errorText": "string",
  "alert": {
    "timestamp": "2024-01-15T09:30:00Z",
    "userId": 1,
    "status": "Active",
    "expression": "string",
    "id": 1,
    "validUntil": "2024-01-15T09:30:00Z",
    "triggerLimits": 1,
    "triggeredCounter": 1,
    "failure": "string",
    "message": "string"
  }
}
```

**SDK Code**

```python
import requests

url = "https://demo.tradovateapi.com/v1/alert/modifyalert"

payload = {
    "alertId": 1,
    "expression": "string"
}
headers = {
    "Authorization": "Bearer <token>",
    "Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.json())
```

```javascript
const url = 'https://demo.tradovateapi.com/v1/alert/modifyalert';
const options = {
  method: 'POST',
  headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
  body: '{"alertId":1,"expression":"string"}'
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}
```

```go
package main

import (
	"fmt"
	"strings"
	"net/http"
	"io"
)

func main() {

	url := "https://demo.tradovateapi.com/v1/alert/modifyalert"

	payload := strings.NewReader("{\n  \"alertId\": 1,\n  \"expression\": \"string\"\n}")

	req, _ := http.NewRequest("POST", url, payload)

	req.Header.Add("Authorization", "Bearer <token>")
	req.Header.Add("Content-Type", "application/json")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(res)
	fmt.Println(string(body))

}
```

```ruby
require 'uri'
require 'net/http'

url = URI("https://demo.tradovateapi.com/v1/alert/modifyalert")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'
request["Content-Type"] = 'application/json'
request.body = "{\n  \"alertId\": 1,\n  \"expression\": \"string\"\n}"

response = http.request(request)
puts response.read_body
```

```java
import com.mashape.unirest.http.HttpResponse;
import com.mashape.unirest.http.Unirest;

HttpResponse<String> response = Unirest.post("https://demo.tradovateapi.com/v1/alert/modifyalert")
  .header("Authorization", "Bearer <token>")
  .header("Content-Type", "application/json")
  .body("{\n  \"alertId\": 1,\n  \"expression\": \"string\"\n}")
  .asString();
```

```php
<?php
require_once('vendor/autoload.php');

$client = new \GuzzleHttp\Client();

$response = $client->request('POST', 'https://demo.tradovateapi.com/v1/alert/modifyalert', [
  'body' => '{
  "alertId": 1,
  "expression": "string"
}',
  'headers' => [
    'Authorization' => 'Bearer <token>',
    'Content-Type' => 'application/json',
  ],
]);

echo $response->getBody();
```

```csharp
using RestSharp;

var client = new RestClient("https://demo.tradovateapi.com/v1/alert/modifyalert");
var request = new RestRequest(Method.POST);
request.AddHeader("Authorization", "Bearer <token>");
request.AddHeader("Content-Type", "application/json");
request.AddParameter("application/json", "{\n  \"alertId\": 1,\n  \"expression\": \"string\"\n}", ParameterType.RequestBody);
IRestResponse response = client.Execute(request);
```

```swift
import Foundation

let headers = [
  "Authorization": "Bearer <token>",
  "Content-Type": "application/json"
]
let parameters = [
  "alertId": 1,
  "expression": "string"
] as [String : Any]

let postData = JSONSerialization.data(withJSONObject: parameters, options: [])

let request = NSMutableURLRequest(url: NSURL(string: "https://demo.tradovateapi.com/v1/alert/modifyalert")! as URL,
                                        cachePolicy: .useProtocolCachePolicy,
                                    timeoutInterval: 10.0)
request.httpMethod = "POST"
request.allHTTPHeaderFields = headers
request.httpBody = postData as Data

let session = URLSession.shared
let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
  if (error != nil) {
    print(error as Any)
  } else {
    let httpResponse = response as? HTTPURLResponse
    print(httpResponse)
  }
})

dataTask.resume()
```