Signed events
Push feedback, failure reports, deleted accounts and plan changes to the watch tower with an HMAC-signed POST.
POST /api/events/{app}
Content-Type: application/json
X-Rem-Timestamp: 1763400000
X-Rem-Event-Id: 6f1c...
X-Rem-Signature: v1=<hex HMAC-SHA256(secret, "<timestamp>.<event id>." + raw body)>
{"kind": "failure_report", "title": "Preview build failed", "summary": "npm install timed out",
"severity": "error", "link": "https://remvibecoder.com/admin/failures/812", "org": "Acme",
"occurred_at": "2026-11-17T10:00:00Z", "actor": {"email": "dev@acme.example"}, "data": {"stage": "install"}}Field | Values |
|---|---|
|
|
|
|
| The record in your app, where an admin acts |
The timestamp must be within 5 minutes; the event id is unique per app (100 characters at most). The secret is per app, made or rotated by a super admin on the Sources page.
Answer | Meaning |
|---|---|
202 | Stored |
200 | The same event id again; nothing changes |
401 | Bad signature or timestamp |
404 | Unknown or inactive app, or no secret set |
413 | Body over 64 KB |
422 | Unknown kind |
429 | Over 120 events a minute for the app |
Server to server only (no CORS). Each accepted event also counts into a daily metric events_<kind>.
Sender in Python
import hashlib, hmac, json, time, uuid, urllib.request
def send(base: str, app: str, secret: str, event: dict) -> int:
body = json.dumps(event, separators=(",", ":")).encode()
ts, eid = str(int(time.time())), uuid.uuid4().hex
sig = hmac.new(secret.encode(), f"{ts}.{eid}.".encode() + body, hashlib.sha256).hexdigest()
req = urllib.request.Request(f"{base}/api/events/{app}", data=body, method="POST", headers={
"Content-Type": "application/json", "X-Rem-Timestamp": ts, "X-Rem-Event-Id": eid, "X-Rem-Signature": f"v1={sig}"})
with urllib.request.urlopen(req, timeout=10) as r:
return r.statusKeep the event id when you retry, so a retry is stored once.
What each app sends: REM CloudHub feedback, failure reports, deleted accounts and plan changes; REM Vibe Coder build and preview failures and feedback; REM Payments plan changes and refund or failed-payment incidents; REM Auth deleted accounts; REM Blogs contacts (optional).
Last updated 18 Nov 2026