Alerts and notifications
An alert rule watches a scope (an event, a saved list, an attraction, a venue or a catalog filter) for one condition and sends
each firing to the channels it picks. Every firing also shows up in the app under Alerts → History, and as a client
webhook alert.fired event if you subscribe to it.
Rules are managed with /v1/alerts/rules (or Alerts → New alert in the app); channels with /v1/channels (Settings → Notifications).
Over the API both need a key with the alerts:write scope.
Channels
Section titled “Channels”A channel is one destination of your organization. Admins add, test, rename, pause and delete them; every member can route rules to them. Chat webhook URLs are secrets: they are stored encrypted and only a non-secret label (the host and a short id) is shown afterwards. When a channel is added, status302 posts a “connected” message to check the URL.
| Platform | kind |
What you paste |
|---|---|---|
| Discord | discord_webhook |
https://discord.com/api/webhooks/… |
| Slack | slack_webhook |
https://hooks.slack.com/services/T…/B…/… |
| Slack (app) | slack_app |
Nothing: with the Slack app installed, pick the channel in Settings → Integrations. |
| Microsoft Teams | teams_webhook |
A Workflows URL (…logic.azure.com/workflows/… or …powerplatform.com/…/workflows/…) |
| Google Chat | google_chat_webhook |
https://chat.googleapis.com/v1/spaces/…/messages?key=…&token=… |
| Telegram | telegram |
Nothing: you get a link that opens the bot in the chat to connect. |
email |
An address; addresses other than your own confirm a 6-digit code. | |
| Web Push | webpush |
Nothing: each browser subscribes from Settings → Notifications. |
The server only accepts webhook URLs on each platform’s official hosts. GET /v1/alerts/options lists which kinds this server has
configured (channelKinds[].enabled).
Channels over the API
Section titled “Channels over the API”An API key with alerts:write lists the channels (GET /v1/channels) to route rules to them by id. Adding, renaming, pausing
(PATCH with enabled: false), testing and deleting channels needs a key created by an owner or admin (a key acts with its
creator’s role, capped at admin); a member’s key gets 403.
curl -X POST -H "Authorization: Bearer $STATUS302_API_KEY" -H "Content-Type: application/json" \ -d '{"kind":"slack_webhook","name":"#ticket-alerts","url":"https://hooks.slack.com/services/T000/B000/XXXX"}' \ https://api.status302.com/v1/channels- Chat webhooks are checked with a “connected” message: a URL the platform rejects answers 422 and no channel is added.
- An
emailchannel added with a key is always confirmed by a 6-digit code sent to the address: pass it toPOST /v1/channels/{channelId}/verify;POST /v1/channels/{channelId}/verificationsends a new code (or a new Telegram link). POST /v1/channels/{channelId}/testsends a test message now and returns the channel with the outcome (lastSentAtorlastError).- An organization has at most 25 channels (409), and verification messages are limited per hour per organization, channel and
address (429 with
Retry-After).
Web Push channels belong to a member’s browser and are only added from the app.
Discord
Section titled “Discord”- Open the channel’s settings (the gear next to its name).
- Go to Integrations → Webhooks → New Webhook.
- Click Copy Webhook URL.
Or let the Discord app set this up: /watch list:<name> creates the webhook, the channel and an activity rule in one go.
- Create an app at
api.slack.com/apps(From scratch) in your workspace. - Open Incoming Webhooks and switch them on.
- Click Add New Webhook to Workspace and pick the channel.
- Copy the
https://hooks.slack.com/services/…URL.
Workflow Builder trigger URLs (/triggers/…) are not incoming webhooks and are rejected.
Or install the Slack app: it posts as status302 to the channels you pick in Settings → Integrations (kind
slack_app, no webhook to paste), and /status302 watch <list> sets up a list feed in one go.
Microsoft Teams
Section titled “Microsoft Teams”- In the Teams channel, open ⋯ (More options) → Workflows.
- Choose Post to a channel when a webhook request is received.
- Name it, confirm the team and channel, and add the workflow.
- Copy the URL it shows.
Office 365 connector URLs (….webhook.office.com) are retired by Microsoft and rejected; create a Workflows webhook instead.
Google Chat
Section titled “Google Chat”- Open the space, then its name → Apps & integrations.
- Under Webhooks, click Add webhook and name it.
- Save, then copy the webhook URL.
Delivery and limits
Section titled “Delivery and limits”Each channel has its own rate limit, below the platform’s: Discord 25 messages a minute, Slack 30, Microsoft Teams and Google Chat 20,
Telegram 18, Web Push 30, and email 20 an hour. Over the limit, or when the platform answers 429, the channel holds its messages for
the platform’s Retry-After and what waits is merged into its next message, so a busy rule never floods a channel.
A webhook the platform answers with 404, 410, 401 or 403 (deleted, or the app removed) disables the channel; its last error is
shown in Settings → Notifications.
Conditions
Section titled “Conditions”type |
Fires when | Scopes |
|---|---|---|
metric |
A market metric (floor, median, sales, inventory, …) crosses a threshold, once per cooldown per event. | every scope |
inventory |
A primary restock of at least minSeats seats in one poll, or a sale burst within windowMinutes. |
event, list, attraction, venue |
activity |
Every change of the chosen market activity kinds that passes the filters. | every scope |
catalog |
A new event, or a new event whose public on-sale is still ahead. | attraction, venue, catalog filter |
Market activity
Section titled “Market activity”An activity condition reports what happened, one line per change (a section, row and price group of seats):
| Activity | What it means | Confidence |
|---|---|---|
primary.restock |
Seats returned or released on the primary market (not cart holds coming back). | Observed |
primary.sale |
Seats still gone from the primary market after the 20-minute hold window. | Inferred: inferred_high when seen between close polls, else inferred_low |
resale.listed |
Seats listed on Ticketmaster resale. | Observed |
resale.sold |
Seats removed from Ticketmaster resale: usually sold, but a seller can also delist. | Always inferred_low |
status302 infers sales from inventory changes; Ticketmaster doesn’t publish them. Treat sale lines as strong signals, not receipts. Resale price changes of a listing that stays up are not reported.
Filters, all optional:
sections: only these section names.minQuantity: only changes of at least this many seats (1 to 10,000; default 1).minPrice/maxPrice: the all-in price per ticket in minor units of the event’s currency (see money).confidence: withprimary.saleor marketplaceresale.sold,any(the default) keeps every sale;highkeeps only sales seen between close polls (and confirmed marketplace sales).
{ "name": "Arena restocks", "scope": { "kind": "event", "ref": "1234" }, "condition": { "type": "activity", "activities": ["primary.restock", "resale.listed"], "maxPrice": 25000 }, "digestSeconds": 30, "channels": [12]}Activity rules have no cooldown: every matching change is reported. A catalog filter scope needs at least one filter (sections,
minQuantity above 1, minPrice or maxPrice) and a digest window of 30 seconds or more, so a broad filter can’t send a message per seat.
When sale alerts arrive
Section titled “When sale alerts arrive”Seats that disappear from primary inventory are first a pending drop: they may be cart holds. On the event page’s inventory
changes they show as “Drop · pending”. Within the 20-minute hold window each drop settles: seats that come back are a
hold released (a cart hold, neither a sale nor a restock, and no alert), seats still gone become a sale. primary.sale
activity rules and inventory sale bursts react to sales only, so their alerts arrive about 20 minutes after the seats disappeared,
not at the drop.
Preview and test a rule
Section titled “Preview and test a rule”POST /v1/alerts/rules/preview takes the body of a new rule and returns what it would match, without saving or sending anything:
{ "items": [{ "event": { "id": 48213, "name": "Arena Tour 2027" }, "detail": "Primary floor $120.00" }], "total": 1, "window": "matching now" }Metric and section conditions list what matches now; restock, activity, sale-burst and catalog conditions list what would have fired
recently (window says over which period). The draft is checked against your plan like a new rule (400, 402).
POST /v1/alerts/rules/{ruleId}/test writes a test firing (test: true) of a saved rule about its best current match, or any upcoming
event in its scope, and delivers it to the rule’s channels and the alerts stream topic, ignoring the cooldown. Use it to check the
routing end to end; it is not sent to alert.fired webhooks. An organization gets 30 test firings per rolling hour (429 with
Retry-After) and test firings are kept 7 days.
Rules that match but don’t fire
Section titled “Rules that match but don’t fire”A rule that matched without firing says why in lastSkip on GET /v1/alerts/rules and GET /v1/alerts/rules/{ruleId} (Alerts in the
app shows it on the rule):
plan: your organization’s current plan doesn’t allow the rule, e.g. an activity rule without market data, or a rule beyond the plan’s rule count (only your first enabled rules run).detailsays what is missing;featureandrequiredPlanname the capability and the plan that includes it. It disappears as soon as the plan allows the rule again.cooldown: a metric or inventory rule fired for that event less than its cooldown ago;untilis when the cooldown ends.
at is when the rule matched (refreshed at most every 5 minutes while the reason stays the same). lastSkip is cleared when the rule
fires and when you change its scope or condition.
Digest windows
Section titled “Digest windows”digestSeconds (0, 30, 60 or 300) holds a rule’s firings for that long and sends them to each channel as one message.
It defaults to 30 seconds for activity rules and 0 (send at once) otherwise.
When a channel’s delivery runs, it sends every delivery of that channel that is due as one message. Activity firings of the same rule
and event become one message with up to 10 lines and “+K more”; other firings become separate embeds, blocks or cards of the same message.
In the history, a delivery that rode along in another one shows coalescedInto (the delivery that carried it); dueAt is the earliest
time a delivery is sent.
Route different events to different channels
Section titled “Route different events to different channels”Each rule has one condition and its own channels. To send different events to different places, create one rule per destination:
| Rule | Condition | Channels |
|---|---|---|
| Restocks and new listings | activity: primary.restock, resale.listed |
Slack #ticket-alerts |
| Primary sales | activity: primary.sale |
Discord #drops |
| Floor watch | metric: primary floor ≤ $120 |
Settings → Notifications shows, under each channel, the rules routed to it and what each one sends. For signed HTTP endpoints of your own, subscribe a webhook to the event types you need instead.
© 2026 status403 Sp. z o.o.Aleja Solidarności 68/121, 00-240 Warsaw, PolandKRS 0001269943NIP 5253108931Share capital PLN 5,000.00
Registry court: District Court for the Capital City of Warsaw, 12th Commercial Division

