shared-signals.dev

Playground · Transmitter

Sample Transmitter

A live SSF Transmitter at https://shared-signals.dev, built to the CAEP Interoperability Profile. Connect your Receiver to it, or drive it from this page: create a stream, then fire any CAEP or RISC event and watch it go out.

Using your own Receiver? Everything on this page goes through the public API, so your Receiver can do the same: discover /.well-known/ssf-configuration, get a token from /ssf/oauth/token with the client credentials below, and create its own stream. See the curl walkthrough.

1. Credentials

There is no sign-up. Any client_id works with any client_secret of 16+ characters; the pair names your private sandbox, so streams created with it are invisible to everyone else. The client_id becomes your streams’ aud. These are kept in this browser only.

2. Create a stream

events_requested — all CAEP and RISC events by default

3. Your streams

4. Fire an event

Connect your own Receiver

Use any client_id and a secret of 16+ characters. Tokens last an hour and carry ssf.read (read config and status, poll) and/or ssf.manage (everything else).

Limits

  • 10 streams per client; 50 undelivered SETs per stream; 30 fired events a minute; 120 API calls a minute per IP.
  • min_verification_interval is 15 seconds. Streams are deleted after 7 days without Receiver activity (inactivity_timeout).
  • Push endpoints must be public https URLs on the default port, by DNS name. Redirects are not followed; failed pushes are retried 4 times over about an hour.
  • default_subjects is ALL: every subject is in every stream until you call subjects:remove.
  • This is a test service. Don’t send real personal data, and don’t rely on it staying up.