AsyncAPI channel · Tarana Wireless · Tarana Cloud Suite — Alert Notification Webhooks

`/{operator-webhook-path}`

A single operator-registered HTTPS endpoint receives every alert type the operator has subscribed that webhook to. TCS POSTs one JSON object per notification.

Open source AsyncAPI → All Tarana Wireless channels Tarana Wireless provider profile

Provider: Tarana Wireless AsyncAPI: v3.0.0 Spec: Tarana Cloud Suite — Alert Notification Webhooks Operations: 1 Messages: 12

Channel address

/{operator-webhook-path}

Parameters

operator-webhook-path — Path component of the operator-registered webhook URL.

Operations

send

sendAlertNotification

TCS sends the notification; the operator endpoint receives it. Retry and signature semantics are not documented by Tarana.

Messages

DEVICE_CONNECTED

TCS alert notification: Device Connected

Content-Type: application/json

DEVICE_DISCONNECTED

TCS alert notification: Device Disconnected

Content-Type: application/json

RN_ETHERNET_PORT_IS_DOWN

TCS alert notification: RN Ethernet Port Down

Content-Type: application/json

RN_ETHERNET_PORT_IS_UP

TCS alert notification: RN Ethernet Port Up

Content-Type: application/json

BN_IS_NOT_REACHABLE

TCS alert notification: BN Not Reachable

Content-Type: application/json

RADIO_CARRIER_MUTED

TCS alert notification: Radio Carrier Down

Content-Type: application/json

RADIO_CARRIER_ENABLED

TCS alert notification: Radio Carrier Up

Content-Type: application/json

CRITICAL_ALARM_RAISED

TCS alert notification: Alarm Raised

Content-Type: application/json

CRITICAL_ALARM_CLEARED

TCS alert notification: Alarm Cleared

Content-Type: application/json

NEW_DEVICE_INSTALLED

TCS alert notification: New Device Installed

Content-Type: application/json

NEW_BN_ONBOARDED

TCS alert notification: New BN Onboarded

Content-Type: application/json

TCA_ALARM_TRIGGERED

TCS alert notification: TCA Alarm Triggered

Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this

find_channelsBrowse and filter every channel in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This channel

curl "https://apis.io/api/v1/channels/operator-webhook-path"

All event channels

curl "https://apis.io/api/v1/channels?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.