Documentation

Your complete guide to using Pagerhooks

Overview

PagerHooks is a webhook event management platform that enables you to create, monitor, and manage webhook endpoints with real-time mobile notifications. When you create a hook in the app, a unique webhook URL is generated that can be used to receive events from external services like Stripe, OpenAI, Google APIs, and more.

Key Features

  • Real-time event tracking and metrics
  • Instant mobile push notifications (iOS)
  • AES-256 encryption for data protection
  • Support for multiple authentication methods (HMAC, Basic Auth, API Keys)
  • Offline-first architecture with real-time sync
  • Full-text search across messages and hooks

Getting Started

Account Creation

  1. Download the PagerHooks app from the App Store
  2. Create an account using your email address
  3. Verify your email through the verification code sent
  4. Set up your password (minimum 8 characters)

Creating Your First Hook

  1. Navigate to the Hooks tab
  2. Tap Create Hook
  3. Select a brand/platform template or use a generic webhook
  4. Configure authentication (recommended)
  5. Copy your generated webhook URL
  6. Add the URL to your external service's webhook settings

Webhook Management

Creating a Hook

When creating a hook, you'll need to provide the following information:

Field Required Description
Name Yes A descriptive label for your hook
Description Yes Details about the hook's purpose
Template/Brand Yes The platform sending webhooks (e.g., Stripe, GitHub)
URL No Optional source URL reference
Authentication No Enable credential-based protection
Secret/Credentials If auth enabled Authentication credentials based on method

Webhook URL Structure

When a hook is created, PagerHooks generates a unique webhook URL that you provide to external services:

https://messages.pagerhooks.com/notifications?id={hook_id}

The id parameter is your unique hook identifier. You can copy this URL directly from the app.

Managing Hooks

View Hook Details:

  • See the webhook URL (tap to copy)
  • View recent messages received by the hook
  • Check hook status (active/inactive)

Edit Hook Settings:

  • Update name, description, and URL
  • Change the brand/template
  • Modify authentication credentials
  • Toggle active status

Delete a Hook:

  • Deleting a hook will also delete all associated messages
  • This action requires confirmation and cannot be undone

Authentication & Security

Supported Authentication Methods

PagerHooks supports multiple authentication methods to secure your webhook endpoints:

Method Description Use Case
Signing Secret HMAC-based signature verification Stripe, GitHub, Slack
Basic Auth Username/password credentials Custom integrations
API Key API key in request header Various APIs
Shared Secret Symmetric secret key Custom webhooks
Webhook ID ID-based authentication Simple integrations
Public Key Asymmetric key verification High-security integrations
Verify Token Token-based verification Facebook, Meta platforms

Protected URLs

When a webhook URL is protected (authentication enabled), every incoming webhook request must include valid credentials that PagerHooks validates on its infrastructure.

How Protected URLs Work:

  1. Credential Configuration: When creating a hook with authentication, you provide the secret/credentials used by the sending service
  2. Request Validation: When a webhook arrives, PagerHooks validates the request signature or credentials against your stored configuration
  3. Rejection of Invalid Requests: Requests that fail authentication are rejected and not stored

Security Warning: If you create a hook without authentication, the app will display a warning: "Using this hook without an authentication field exposes it to higher risk of receiving unsolicited events."

Credential Storage

PagerHooks implements multiple layers of security for credential storage:

  • AES-256 Encryption: All secrets are encrypted at rest
  • Masked Display: Credentials are displayed as asterisks in the UI to prevent accidental exposure
  • Secure Updates: Credential updates are processed through secure edge functions
  • No Plain-Text Transmission: Secrets are never transmitted in plain text after initial storage

Plans & Rate Limits

Free Plan

Best for personal use

$0/month

  • ✓ 500 events/month
  • ✓ 1 webhook endpoint
  • ✓ 7 days log retention
  • ✓ Mobile notifications
  • ✓ Advanced authentication

Pro Plan

Coming Soon

Best for small teams

$12/month

  • ✓ 10,000 events/month
  • ✓ 3 webhook endpoints
  • ✓ 30 days log retention
  • ✓ Mobile notifications
  • ✓ Advanced authentication

Rate Limiting

What Happens When You Hit the Limit:

  • Events exceeding your monthly cap will not be stored
  • You'll receive a notification when approaching your limit
  • Upgrade to Pro for higher limits

Log Retention:

  • Free Plan: Events older than 7 days are automatically deleted
  • Pro Plan: Events older than 30 days are automatically deleted

Messages & Events

Viewing Messages

Messages are webhook events received by your hooks. Each message contains:

Field Description
Payload The JSON data sent by the webhook
Tag Event type or category label
Hook Name The associated hook that received the event
Brand The platform that sent the webhook
Timestamp When the event was received
Read Status Whether the message has been viewed

Message Management

Individual Actions:

  • View full JSON payload as formatted tree
  • Mark as read/unread
  • View similar messages from the same hook

Bulk Actions:

  • Select multiple messages
  • Share messages
  • Export messages
  • Mark all as read/unread
  • Delete selected messages

Search:

  • Full-text search across all messages
  • Search by hook name, event type, or payload content

Support & Resources

Need help or have questions? We're here to assist you.