Scouttlo
ENES
All ideas/integration, notifications/A SaaS platform offering secure, manageable webhook services for app events with automatic retries and accessible delivery logs.
GitHubB2BDevToolsintegration, notifications

A SaaS platform offering secure, manageable webhook services for app events with automatic retries and accessible delivery logs.

Scouted 7 hours ago

7.0/ 10
Overall score

Turn this signal into an edge

We help you build it, validate it, and get there first.

From detected pain to an actionable plan: who pays, which MVP to launch first, how to validate it with real users, and what to measure before spending months.

Expanded analysis

See why this idea is worth it

Unlock the full write-up: what the opportunity really means, what problem exists today, how this idea attacks the pain, and the key concepts you need to know to build it.

We'll only use your email to send you the digest. Unsubscribe any time.

Score breakdown

Urgency8.0
Market size6.0
Feasibility9.0
Competition5.0
The pain

Third-party integrations lack real-time notifications for raffle state changes and must repeatedly poll the API.

Who'd pay

Developers and companies integrating raffle systems, bots, dashboards, or analytics tools needing real-time event notifications.

Signal that triggered it

"Third-party integrations (bots, dashboards, analytics tools) currently have no way to receive real-time notifications when a raffle transitions state (e.g. `active` → `ended`, winner drawn). They must poll `GET /raffles/:id` repeatedly."

Original post

Add webhook support for raffle state-change events

Published: 7 hours ago

Repository: crackedstudio/tikka Author: Otaiki1 Summary Third-party integrations (bots, dashboards, analytics tools) currently have no way to receive real-time notifications when a raffle transitions state (e.g. active → ended, winner drawn). They must poll GET /raffles/:id repeatedly. Location backend/src/api/rest/raffles/raffles.module.ts backend/src/api/rest/raffles/raffles.service.ts backend/src/services/notification.service.ts Proposed Solution 1. Add a webhooks table in Supabase: { id, owner_address, target_url, events[], secret, created_at }. 2. Create WebhookService that signs payloads with HMAC-SHA256 and POSTs to registered URLs. 3. Expose CRUD endpoints under /webhooks (authenticated, owner-scoped). 4. Trigger delivery from RafflesService (or the notification pipeline) on state change. 5. Implement exponential back-off retry (3 attempts) and disable webhooks that consistently fail. Acceptance Criteria - Webhook CRUD endpoints work behind JWT auth - Payload is signed with X-Tikka-Signature header - Failed deliveries are retried up to 3 times with back-off - Delivery log is queryable by the webhook owner

View on github ↗
Your daily digest

Liked this one? Get 5 like it every morning.

SaaS opportunities scored by AI on urgency, market size, feasibility and competition. Curated from Reddit, HackerNews and more.

Free. No spam. Unsubscribe any time.

Open source ↗