Control the overlay from a Stream Deck.

TL;DR

1. Install a generic HTTP request plugin on your Stream Deck (BarRaider's free Web Requests, for example).
2. In the WES Alert dashboard, open the Stream Deck tab and copy the URL of the action you want.
3. Copy the Authorization header value from the same tab (shown once you confirm the secret warning).
4. On the key: method POST, paste the URL, add the header Authorization with the copied value. Done.

The native "Website" action is not enough. The built-in Stream Deck "Website" action only opens a browser page. WES Alert needs a POST request with an Authorization header, which that action cannot send. Any plugin that supports POST plus custom headers works.

What a key can do

Every action is a POST to one URL. All the URLs are copied ready-made from the dashboard's Stream Deck tab; you never build them by hand.

• Apply profile Applies one of your saved profiles to the live overlay: pack, colors, placement, sound, everything the profile captured. One key per profile.
• Pause Pauses alerts. Incoming alerts are held in the buffer until you resume.
• Resume Goes back live and releases the buffer.
• Quick Pause Pauses for a fixed window, then auto-resumes. Uses the duration from Settings › Broadcast (a per-key override exists, see below).
• Next alert While paused, lets exactly one buffered alert through.

Double press is harmless. Applying a profile that is already active re-pushes the same state, pausing while paused is a no-op, and a second quick pause just re-arms the window.

What you need

• A Stream Deck (any model) with the Stream Deck software installed.
• A generic HTTP request plugin from the official Stream Deck store. We recommend BarRaider's Web Requests: free, and it supports POST requests with custom headers, which is all WES Alert needs.
• Your WES Alert Dashboard open once, to copy the URLs and the Authorization header.

Everything you copy lives in the dashboard

Open the dashboard and switch to the Stream Deck tab (top navigation). It groups everything a key needs:

• Profiles: one apply URL per saved profile, with a copy button. The same URL is also available from each profile's pencil menu on Main, under "Stream Deck".
• Broadcast: the director command URLs (Pause, Resume, Quick Pause, Next alert).
• Authorization: the header value, masked by default. Clicking copy shows a secret warning first, then copies the full value (Bearer followed by your Stream Key). It is the same header for every key: copy it once, reuse it on each key.
• Your Deck: the suggested-layout preview is clickable too; pressing a key in it copies that key's URL.

The Stream Key itself can also be viewed and copied from Settings › Connection (it is the same key Streamer.bot uses). The Stream Deck tab is more convenient because it copies the full Bearer … header value directly.

Configure a key, step by step

The steps below use BarRaider's Web Requests; other HTTP plugins expose the same three fields under different names (method, URL, headers).

1. Put a Web Requests action on a key. In the Stream Deck software, find Web Requests in the actions list (after installing it from the store) and drag it onto a free key.
2. Set the request. Method POST (not GET; the request is rejected otherwise). URL: paste the one you copied from the dashboard. Headers: one header, Authorization, with the value copied from the Stream Deck tab; it already includes the Bearer prefix. The request body stays empty (one exception below).
3. Press the key. With your overlay loaded in OBS, press it. A profile apply takes effect immediately (if an alert wave is playing, the pack swap waits for the wave to finish, then swaps). Director commands show up in the dashboard's broadcast banner within a couple of seconds.

Naming your keys. The key title is yours to choose; the URL decides what happens. A layout that works well: one row of profile keys (per scene: gameplay, break, just-chatting), one row of broadcast keys. The Stream Deck tab's "Your Deck" module shows a suggested layout based on your actual profiles.

Optional: a custom Quick Pause duration on one key

By default, quick pause uses the duration configured in Settings › Broadcast. A specific key can override it by sending a small JSON body with the request:

Content-Type: application/json

{"duration": 30000}

duration is in milliseconds, accepted between 5000 (5 s) and 300000 (5 min). A value outside that range is silently ignored and the default applies. Remember to also set the Content-Type: application/json header on that key, otherwise the body is not read. This lets you have, say, a 30 s key and a 5 min key side by side.

When a key press fails

The Stream Deck only shows OK or error, based on the HTTP status code. Here is what each code means and what to do:

200 · Done

The action was applied. Nothing to do.

400 · No overlay connected

For director commands: no overlay is connected (or the action segment of the URL has a typo). Open OBS first, with your WES Alert overlay source active; broadcast commands need a connected overlay to talk to.

401 · Wrong Stream Key

The Stream Key in your Authorization header is wrong, usually because it was regenerated since you configured the key. Re-copy the header value from the dashboard's Stream Deck tab and update every configured key.

403 · Subscription inactive

Your subscription is not active. Check your account status in the dashboard.

404 · Profile not found

The profile in the URL no longer exists (deleted or recreated). Copy the fresh apply URL from the Stream Deck tab. Profile URLs survive renames, but not deletion.

409 · Pack unavailable

The profile's pack is no longer available on your account. Open the profile in the dashboard and re-save it with an available pack.

429 · Rate limited

Too many requests in a short burst. Wait a few seconds and press again. Normal use never hits this.

Your Stream Key is a secret

Anyone who has your Stream Key can apply profiles, pause your alerts and push events to your overlay. Treat it like a password: do not show it on stream (the dashboard masks it for exactly that reason), do not paste it in chat or in screenshots of your Stream Deck config.

If the key leaks, regenerate it in Settings › Security (Stream Key row). Be aware of the blast radius: regenerating breaks every Stream Deck key configured with the old value, plus your Streamer.bot integration if you use it. After regenerating, re-copy the header value from the Stream Deck tab and update each key. The full rotation procedure is in the Security guide.