Home API

API

Comprehensive guides to Reply's API: request and response examples, rate limits, full methods list, troubleshooting, and more.
4 articles

Webhooks page overview

The Webhooks page lets you manage all V3 webhook subscriptions in one place. You can create and edit webhooks, send test payloads, monitor failures, and manage subscriptions created both in Reply and via API tools such as Postman. You can find the page under Execution → Webhooks. Create a webhook To create a new webhook: 1. Go to Execution → Webhooks. 2. Click Add new. 3. Select an event from the dropdown. 4. Enter the endpoint URL. 5. Select scope and payload options (as defined in the API documentation). 6. Choose whether to enable the webhook upon creation. 7. Click Create. Once created, the webhook will appear in the list. Manage webhooks You can manage each webhook directly from the Webhooks page. Use the toggle to activate or deactivate a webhook. To update the event, URL, scope, or payload settings, click Edit. To delete a webhook, click the bin icon. Please note that you can only see and manage your own webhooks, not webhooks created by other team members. Send test payload You can test a webhook at any time. To send a test payload, click Send test payload. A sample payload with test data will be sent. You can also view example payload data in the same view. Failure logs If a webhook fails, you can review the issue in the Failure logs section. Here you can see failed webhook attempts, view error details, and identify and fix delivery issues. Migration from V2 webhooks Webhooks are not automatically migrated from V2. If you still have V2 webhooks, they will be shown on the page so you can recreate them as V3. To fully switch to the new version: 1. Recreate webhooks as V3 on the Webhooks page. 2. Delete V2 webhook subscriptions. Once no V2 webhooks remain, the migration banner will no longer be shown.

Last updated on Oct 22, 2026

Webhooks

Webhooks let web applications communicate with each other. In Reply, webhooks send real-time data to your application whenever an event occurs. Each webhook notification includes: - The type of event - Data related to the event Your webhook endpoint can then take further actions based on this information. Here's a short video tutorial explaining what webhooks are, the types available in Reply, how to subscribe to them, and more: https://www.youtube.com/watch?v=NyU_A1QDLG0 What can I do with webhooks? With webhooks, you can: - Integrate Reply with third-party tools - Receive notifications about events in your Reply account - Replace some Zapier integrations How do I start using webhooks? To use webhooks, you need your Reply API key: 1. Go to Settings → API Key in your Reply account. 2. Copy your API key to use in your webhook endpoint. Available webhook types Reply supports the following webhook events: Email events - email_replied – triggered every time a prospect replies to an email. - contact_replied – triggered whenever a contact's status changes to Replied. - reply_categorized – triggered when a reply is categorized with a new inbox category - email_sent – triggered when a new email is sent (first step or follow-up) - email_opened – triggered when a prospect opens your email - contact_opted_out – triggered when a prospect opts out - contact_finished – triggered when a prospect finishes a sequence - contact_called – triggered when a cloud call is made or logged - email_link_clicked – triggered when a link in an email is clicked - email_account_connection_lost – triggered if the connection to an email account is lost - email_account_error – triggered when the email provider returns an error - email_bounced – triggered when an email fails to deliver LinkedIn events - linkedin_connection_request_sent – triggered when a connection request is sent - linkedin_message_sent – triggered when a LinkedIn message is sent - linkedin_connection_request_accepted – triggered when a connection request is accepted - linkedin_message_replied – triggered at the first reply to a LinkedIn message in a sequence - linkedin_reply_categorized – triggered when a LinkedIn reply is categorized - linkedin_account_alerts - triggered when Sales Navigator is disconnected, weekly connection-request limit reached, or InMail credits exhausted. - linkedin_comment_posted – triggered when an AI-generated comment is posted on a contact's LinkedIn post. Other events - autopilot_stopped – triggered when Autopilot stops in a sequence. It fires on the first stop and includes the reason why Autopilot was stopped. 👉 Check out our API documentation for a complete guide on webhook subscriptions.

Last updated on Oct 22, 2026