Design a Resilient Webhook Ingestion Endpoint
Get a complete technical design for a webhook ingestion system featuring signature verification, idempotency logic, and a robust retry strategy.
Prompt
Act as a Senior Backend Engineer. Design a resilient webhook ingestion endpoint that handles incoming POST requests, verifies authenticity, and manages failures. Follow these rules: 1. Use HMAC-SHA256 for signature verification. 2. Define an idempotency key lifecycle using a Redis-based locking strategy. 3. Provide an exponential backoff schedule including jitter calculations. 4. Include a table showing HTTP response codes for specific failure states. Output format: 1. Security Logic: Detailed steps for signature verification. 2. Idempotency Flow: A numbered list of the request processing lifecycle. 3. Retry Strategy: A table with retry attempt counts and delay times in seconds. 4. Error Handling: A table mapping error types to HTTP status codes. This is for technical architectural purposes only and does not replace production security audits.Example output
Tips and common edits
Why this works
- Forces a structured architectural approach to common distributed system failure points.
- Provides concrete logic for security and idempotency that can be directly implemented.
- Uses tables for retry and error handling to ensure clarity and quick reference.
Use this prompt in ChatGPT, Claude, or Gemini when you are building a service that must reliably receive and process third-party webhooks. No input is required; the output provides the core architectural blueprint and logic.
Common edits
- Adjust the Redis TTL based on your specific business requirements for data retention.
- Modify the HMAC algorithm if your specific third-party provider requires a different standard.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Design a resilient background job and retry system
Get an end-to-end background processing architecture that prevents duplicate actions, handles transient failures, and safely manages poison pills.
Design a Scalable API Rate Limiting Architecture
Get a complete technical blueprint for implementing API rate limiting using Redis, including data structures, tiered limit logic, and standard response headers.
Design a Scalable Append-Only Audit Logging System
Get a structured, immutable schema design for tracking sensitive data changes, including field-level diffs and compliance-ready partitioning strategies.
Design Cursor-Based Pagination Logic for High-Volume APIs
Get a complete implementation plan for cursor-based pagination including SQL queries, cursor encoding logic, and strategies for handling record deletions.
Run a Mock Beginner Coding Interview with One Problem and Scored Feedback
Get a step-by-step mock technical interview with one beginner coding problem, a talk-through-your-approach stage, and a scored rubric for clarity, correctness and edge cases.
Turn a Feature Description into a REST API Endpoint Spec
Paste a feature description and get a REST API spec with a route table, request and response fields, status codes, exact validation rules, and open questions on auth and pagination.
- Write a README From Your Code and Notes Without Invented Commands
- Trace an execution path from entry to database
- Generate complete API documentation from route code
- Design Standardized REST API Error Contracts Using RFC 7807
- Batch Rename Files in a Folder with a Script You Can Preview First
- Build an Excel Formula from a Plain-English Description of What You Need