Create Test Messages - Social Stream Ninja

What This Tool Does

The Create Test Message page sends synthetic Social Stream payloads to your dock, overlays, alerts, or Event Flow setup. Use it to test without waiting for a real chat message, donation, membership, raid, reward, or other event.

Use a test session when possible. A submitted message behaves like incoming session traffic and can trigger alerts, sounds, webhooks, OBS actions, or other automations.

Quick Start For SSApp Or The Extension

Open Social Stream Ninja and make sure the service is active.
Under Global settings and tools → Mechanics, enable remote API control of extension. SSApp uses the same setting name.
Copy your Session ID from Social Stream or from the session= value in your dock or overlay URL.
Open Create Test Message and enter that Session ID.
Leave Send Via set to Extension API ingest for normal testing.
Choose a preset, adjust its fields, and select Load Preset.
Review the Payload JSON, then select Submit.
Confirm the item appears in the dock or target overlay and that the expected automation runs.

You can include the session in the URL: createtestmessage.html?session=YOUR_SESSION_ID.

Example: One Fake 1,000 KICKs Message

This creates one Kick-style support message worth 1,000 KICKs. It does not create 1,000 separate messages.

Choose the Chat Message preset.
Set Type to Kick.
Enter a test name and message.
Set Has Donation to 1000 KICKs.
Select Update JSON from Fields, verify the JSON, and submit it.

The minimal payload is:

{
  "type": "kick",
  "chatname": "Test Supporter",
  "chatmessage": "Thanks for the stream!",
  "hasDonation": "1000 KICKs"
}

Use Chat Message for this example. The Donation / Cheer preset includes Twitch-specific cheer fields.

Using Presets And Custom JSON

Presets provide a starting payload for common cases such as donations, subscribers, gifted subscriptions, raids, rewards, viewer updates, first-time chatters, and train events.

Load Preset replaces the JSON with the selected preset and current field values.
Update JSON from Fields builds a basic message from the visible fields.
You can edit Payload JSON directly when testing a specific field or event shape.
hasDonation carries the visible support amount, such as 1000 KICKs or $10.00.
Only include event when you are testing a real named event. A normal donation-style chat row can use hasDonation by itself.

For field definitions and real platform examples, see the Event Reference.

Choose The Right Delivery Mode

Send Via	Use It When	Required Setup
Extension API ingest	Testing normal docks, overlays, alerts, Event Flow, or SSApp.	Same Session ID and remote API control of extension enabled.
Direct to channel 1	The target dock was opened with `&server`.	The target must be listening on the matching server channel.
Direct to channel 4	Testing a target that uses `&server2`, including compatible event pages.	The target must be listening on the matching server channel.

If you are unsure, use Extension API ingest.

Common Fixes

Nothing appears: confirm the target page is open and uses the same Session ID.
Extension API ingest fails: enable remote API control of extension, then reload the dock or overlay and try again.
Direct mode says sent but nothing appears: use Extension API ingest unless the target URL has the matching &server or &server2 mode.
Wrong event fires: inspect the Payload JSON for leftover fields from another preset.
Kick test behaves like Twitch: use the Chat Message preset and set type and hasDonation as shown above.
An automation runs more than once: check whether multiple docks, action pages, or Event Flow instances are open on the same session.