Webhooks
The signed webhooks REM Vibe Coder receives and sends - payment events from REM Payments, content revalidation from REM Blogs, and the REM Platforms event feed.
REM Vibe Coder exchanges signed webhooks with the other REM Platforms services. They connect the services to each other; there are no per-person webhook subscriptions to set up in Vibe Coder today. To react to your own builds from your code, follow the run's events (see Run events).
All three use HMAC-SHA256 over the raw body, so a receiver must verify the signature before parsing JSON, and must reject old timestamps.
Payment events (REM Payments → Vibe Coder)
Endpoint |
|
Sent by | REM Payments, for the app |
Signed with | The webhook secret REM Payments gave Vibe Coder when it linked itself (kept sealed at rest) |
Events |
|
Vibe Coder verifies the signature with the REM Payments SDK, ignores an event it has already processed (same event id) and updates the payer's plan state (plan, status, period end, cancel at period end, last payment status). Credits are never stored in Vibe Coder: the balance is always read from REM Payments' one REM Credits ledger.
Content revalidation (REM Blogs → Vibe Coder)
Endpoint |
|
Sent by | REM Blogs when a post, docs page or legal page of the product |
Header |
|
Effect | The cached blog, docs, legal pages and the sitemap are refreshed at once instead of within five minutes |
This is why a page published in REM Blogs shows on remvibecoder.com/docs and /blog right away.
REM Platforms event feed (Vibe Coder → REM Platforms)
Failure reports (builds and previews that end failing, kind failure_report) and feedback (kind feedback) sent from the account menu go to REM Platforms (the operators' watch tower), two ways:
Pull. GET https://remvibecoder.com/api/platform/v1/events?days=30 with Authorization: Bearer vcp_… (a read-only token an operator creates with manage.py platform_token). Answer:
{"daily": [], "snapshots": {}, "events": [{"app": "vibecoder", "id": "…", "kind": "failure_report", "severity": "error", "title": "…", "summary": "A Vibe Coder build ended failed (code: workflow_test).", "link": "…", "org": "", "actor_email": "…", "occurred_at": "2026-11-18T10:21:04Z", "data": {"what": "build", "run_id": "…", "code": "workflow_test", "failure_kind": "code"}}]}Push. When configured, each new event is posted to POST <watch tower>/api/events/vibecoder with:
Header | Value |
|---|---|
| Unix seconds when it was signed |
| Vibe Coder's event id (a resend of the same id is a no-op) |
|
|
Verifying in Python:
import hmac, hashlib
def valid(secret: str, ts: str, event_id: str, raw: bytes, header: str) -> bool:
mac = hmac.new(secret.encode(), f"{ts}.{event_id}.".encode() + raw, hashlib.sha256).hexdigest()
return hmac.compare_digest("v1=" + mac, header)Failed pushes are retried (up to six attempts) and a sweep sends whatever is left; recording an event never fails a build.