Send alerts from your own bot

Copy your strategy webhook URL

In Nyria, open your strategy and go to the Integration tab. Copy the webhook URL. It looks like this:

https://trades.nyria.io/webhooks/4f9c2a91b7d34e0fae9c1b6d2e8f0a4c8e1b7d34e0fae9c1b6d2e8f0a4c9b3d2

The part after /webhooks/ is your strategy's webhook token (tokenHash). It's the only authentication on the request: there is no Authorization header.

Send the smallest payload

The smallest valid body has two fields, ticker and action. In a terminal, run:

curl -X POST https://trades.nyria.io/webhooks/REPLACE_WITH_YOUR_TOKEN \
  -H "Content-Type: application/json" \
  -d '{
    "ticker": "AAPL",
    "action": "buy"
  }'

Replace REPLACE_WITH_YOUR_TOKEN with the webhook token from step 1. Nyria finds the strategy by token, matches buy to your entry rule, sizes the order from the bot's settings, and sends it to the connected broker.

The alert shows in the strategy's Logs tab within a second.

Set the order type for a single alert

The bot's budget per entry always sets the size, and no field in an alert changes it. You can set the order type per alert:

curl -X POST https://trades.nyria.io/webhooks/REPLACE_WITH_YOUR_TOKEN \
  -H "Content-Type: application/json" \
  -d '{
    "ticker": "AAPL",
    "action": "OPEN",
    "direction": "LONG",
    "order_type": "limit",
    "price": 340.50
  }'

• order_type: market or limit. Leave it out to use the strategy's order type. Nyria reads it on an alert that names action and direction, as this one does. On an options strategy set to Provided in alert it's ignored, and the strategy's order type applies. See when Nyria reads order_type.
• price: the limit price. Required when order_type is limit.
• How long an order stays open comes from the strategy's Duration setting (Day, Good till canceled or Fill or kill); the alert has no field for it.

Send a plain-text body instead of JSON

JSON is the better format, but if your source can only send free text (older alert tools, some IFTTT or Zapier steps), Nyria reads plain text too:

curl -X POST https://trades.nyria.io/webhooks/REPLACE_WITH_YOUR_TOKEN \
  -H "Content-Type: text/plain" \
  --data-binary "AAPL long entry"

Nyria reads the ticker (AAPL), the direction (long) and the action (entry). Set Content-Type: text/plain so Nyria does not try to decode the body as JSON.

Paste the text into the alert tester first to see how Nyria reads it.

Make repeat sends safe

If your script retries after network failures, or your provider delivers the same alert twice, Nyria catches it. An identical body received again within 30 seconds, or within 5 minutes with no other alert in between, counts as a duplicate, and only the first one places an order.

Nyria matches duplicates on metadata.message_id when you send one, and on a hash of the whole body when you do not. To scale into the same position, the body has to differ. Set a unique metadata.message_id:

curl -X POST https://trades.nyria.io/webhooks/REPLACE_WITH_YOUR_TOKEN \
  -H "Content-Type: application/json" \
  -d '{
    "ticker": "AAPL",
    "action": "OPEN",
    "direction": "LONG",
    "metadata": { "message_id": "scale-in-2027-06-04T13:31:15Z" }
  }'

Anything unique works: a counter in your script, a timestamp, or a new UUID per alert.

Handle the response

Nyria answers with an HTTP status code and a JSON body. Have your sender log or alert on non-2xx responses.

A minimal Python sender that reports failures:

import requests

WEBHOOK_URL = "https://trades.nyria.io/webhooks/REPLACE_WITH_YOUR_TOKEN"

def fire_alert(payload: dict) -> None:
    r = requests.post(WEBHOOK_URL, json=payload, timeout=10)
    r.raise_for_status()
    status = r.json().get("status")
    if status == "processed":
        print("Nyria read the alert")
    else:
        print(f"Nyria did not act on it: {r.json()}")

fire_alert({"ticker": "AAPL", "action": "OPEN", "direction": "LONG"})

raise_for_status() turns 4xx and 5xx into exceptions your retry logic can see. It does not catch a rejection or a duplicate, which answer 200, so check status too. Always set a timeout. Nyria answers quickly, but a hung socket can stall your sender.

Confirm the order in the broker

Open your broker dashboard, or the bot in Nyria, and check the order is there. With the curl from step 2 on a paper account, you see an AAPL market buy at the bot's size.

If the order is not there, check the strategy's Logs tab. Each alert has a row there, and a rejected or failed one carries its reason. Duplicate deliveries are logged at most once every 5 minutes, so a missing row can also mean a duplicate.