Dashboard guide

From sign-up to your first message

1. Sign up at https://app.webhookadmin.com/signup and create an organization (Organizations, projects and environments).
2. Create a project for each service that sends webhooks. Each project gets a live and a test environment.
3. Add a customer, then add an endpoint (the URL that receives webhooks) for that customer.
4. Create an API key and send messages from your server with the API.
5. Check the results in Messages.

Each project’s Overview shows “Steps to your first message” and marks finished steps as Done.

How the dashboard is organized

Use the switcher at the top of the left menu to change the organization, project and environment (live or test). The menu items depend on whether a project is selected.

Open this guide from Guide in the menu. The menu under your email address at the bottom lets you choose the theme (System, Light, Dark), the language, Account settings and Log out. On a phone, open the menu with the button at the top left.

All pages

Basics

• Overview: What the Overview shows for the whole organization and for each project, and how to follow up on endpoints that need attention.
• Organizations, projects and environments: Create, switch, rename and delete organizations and projects, and how live and test environments differ.

Sending webhooks

• Customers: Register and delete the companies or users that receive your webhooks (customers), per environment.
• Endpoints: Add an endpoint (where webhooks are delivered) for a customer, and change its signing secret, events and delivery settings.
• Event types: Register the names of the events you send (event types), such as invoice.paid, per environment, and edit their descriptions or archive them.
• Messages: Check the status, attempts and payload of messages you sent, and send test messages.
• Retries and recovery: How automatic retries work, and how to resend failed messages one at a time or for a whole endpoint.
• Customer portal: Issue a customer portal link so a customer can manage their own endpoints, signing secrets and delivery logs.
• Fixed source IP: Send from a fixed source IP (209.71.107.233) for customers who allow only specific IP addresses.
• Transformations: Run a JavaScript handler right before each delivery to change the payload, headers, URL or HTTP method, or to cancel the delivery.

Receiving webhooks

• Sources (inbound): Receive webhooks from services such as Stripe or GitHub, verify their signatures, and deliver them to a customer’s endpoints.

Operations

• Alerts: Get notified about failed deliveries, automatically disabled endpoints and more via Slack, Teams, Chatwork, email or webhook.
• API keys: Create and revoke the API keys your sending server uses to call the API, per environment.
• API logs: Find the cause of failed API calls (such as 401 or 422) and how to fix them in API logs.

Organization and account

• Members and roles: Invite members to your organization, change or remove their roles, and what each of the four roles can do.
• Single sign-on: Let your members sign in with an identity provider such as Okta, Microsoft Entra ID or Google Workspace.
• Plans and billing: Change or cancel your plan, manage your card and invoices, and choose what happens when you reach your monthly limit.
• Account settings: Change your name, login methods, passkeys, connected apps, language and theme, and delete your account.