Use a Custom Webhook Source

Copy your strategy webhook URL

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

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

The path segment after /webhooks/ is your strategy's token hash (tokenHash), a 64-character lowercase hexadecimal string with no prefix. It's the only authentication on the request, so treat it like a password. There is no separate Authorization header.

Send the minimum-viable payload

The smallest valid body is two fields: ticker and action. Open a terminal and 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 token hash you copied in Step 1. Nyria looks up the strategy by token, matches buy against your entry rule, builds the order using the strategy's position-sizing config, and forwards it to the connected broker.

You should see the alert show up in the strategy's Logs tab within a second or two.

Set the order type for a single alert

Position size always comes from the bot's sizing config; no field in an entry alert changes it. What you can set per alert is the order type:

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": 175.50
  }'

• order_type: market or limit. Omit it to use the strategy's configured type.
• price: the limit price. Required when order_type is limit.
• duration: day, gtc, or fok. Default is day.

Send a plain-text body instead of JSON

JSON is the recommended format, but if your source can only emit free-form text (older alerting platforms, some IFTTT/Zapier steps), Nyria's parser also reads plain text:

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

The parser extracts the instrument (AAPL), the direction (long), and the action (entry). Set Content-Type: text/plain so Nyria doesn't try to JSON-decode the body.

Make repeat sends safe

If your script retries on network failures (or your provider delivers the same alert twice), Nyria's default behavior protects you: an identical body received again within about five minutes is treated as a duplicate, and only the first one places an order.

The dedup key is metadata.message_id when you send one, and a hash of the whole body when you do not. So if you actually want 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-2026-06-05T09:31:15Z" }
  }'

Anything unique works: a counter your script tracks, a timestamp, or a UUID minted per alert.

Handle the response

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

A minimal Python sender that surfaces 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 parsed 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/5xx into exceptions so your retry logic can see them. It will not catch a rejection or a duplicate: those answer 200, so check status as well. Always use a finite timeout. Nyria responds quickly, but a hung socket can wedge your producer.

Confirm the order in the broker

Open your broker dashboard (or the Nyria app's bot view) and verify the order landed. If you used the curl from Step 2 against a paper account, you should see an AAPL market buy at the strategy's default size.

If the order is not there, check the strategy's Logs tab. A parsed alert is logged at INFO, a rejection at WARN with its reason, and a failure at ERROR. Duplicate deliveries are logged at most once every few minutes, so a missing row can also mean a duplicate.