Playground · Receiver
Sample Receiver
A push endpoint (RFC 8935) for testing your Transmitter. Every SET that arrives is decoded, its signature checked against your issuer’s keys, and its claims checked against SSF 1.0, CAEP and the Interoperability Profile — with the exact response your Transmitter got.
Create a receiver
Both fields are optional. Set them and the receiver rejects SETs whose iss or aud don’t match, as a real Receiver must.
Your receiver
Create a stream on your Transmitter with push delivery to this endpoint, and set
delivery.authorization_header to the value below. Anyone with this page’s link can see what arrives, so don’t send real user data.
Receivers are deleted after 7 days without use.
Received SETs
What gets checked
- Transport:
Authorizationheader,Content-Type: application/secevent+jwt. - JOSE header:
typissecevent+jwt,algisRS256, akidis present. - Signature: keys found by SSF discovery from the SET’s
iss(/.well-known/ssf-configuration→jwks_uri). - Claims:
iss,aud,iat,jti, a top-levelsub_id, nosuborexp,txnrecommended. - Event: exactly one event, a known type, its required claims, and
reason_adminon CAEP events.
A SET that fails gets 400 with an RFC 8935 error (invalid_key, invalid_issuer, invalid_audience,
invalid_request); one that passes gets 202 Accepted. Warnings don’t cause a rejection.
To check a SET without sending it, use the SET inspector.