Skip to main content

Overview

The Webhooks API allows you to configure endpoints that receive real-time HTTP notifications when events occur in your InstaView account. Webhooks provide an event-driven alternative to polling, enabling immediate integration with your systems.

Resource Structure

Required Scopes

Creating Webhooks

Basic Webhook

Comprehensive Webhook Configuration

Important: The signingSecret is only returned once during webhook creation. Store it securely immediately. If you lose it, you must delete and recreate the webhook.

Listing Webhooks

List All Webhooks

Monitor Webhook Health

Updating Webhooks

Partial Update

Update Custom Headers

When updating headers, the entire headers array is replaced. Include all headers you want to keep.

Event Types

Event Type Reference

Event Selection Strategy

Subscribe only to completion events:
Use case: Simple integrations that only need final results

Circuit Breaker

The circuit breaker protects both systems from cascading failures:

How It Works

1

Failures Accumulate

Each failed delivery increments consecutiveFailures
2

Circuit Opens

After threshold failures, circuitOpenedAt is set and deliveries stop
3

Deliveries Paused

No new deliveries are attempted while circuit is open
4

Manual Reset

Use the reset endpoint to re-enable after fixing issues

Monitoring Circuit State

Resetting Circuit Breaker

Testing Webhooks

Send Test Ping

The webhook must be subscribed to the ping event (type 2) for testing to work.

Test Response Structure

Or on failure:

Deleting Webhooks

Delete a Webhook

Deleting a webhook immediately stops all deliveries. Pending deliveries will not be sent.

Custom Headers

Supported Headers

You can add custom headers for authentication or routing:

Sensitive Headers

The following headers are automatically encrypted at rest:
  • Authorization
  • X-API-Key
  • X-Secret
  • API-Key
When listing webhooks, these headers show isMasked: true and their values are hidden.

Header Limits

  • Maximum 50 custom headers per webhook
  • Header names: 1-255 characters
  • Header values: 1-4096 characters

Configuration Fields

url
string
required
The HTTPS endpoint URL to receive webhook notifications (max 2048 characters)
events
array
required
Array of event type IDs to subscribe to (0-5)
name
string
Human-readable name for the webhook (max 255 characters)
description
string
Description of the webhook’s purpose
headers
array
Custom headers to include in requests (max 50 headers)
isActive
boolean
Whether the webhook is active (default: true, can be updated)

Response Fields

id
string
Unique identifier for the webhook configuration
apiKeyId
string
The API key ID this webhook belongs to
companyId
string
Company ID this webhook is associated with. Null if webhook receives events for all companies (global webhook).
maxRetries
number
Maximum retry attempts for failed deliveries (system-configured)
timeoutMs
number
Request timeout in milliseconds (system-configured, default 30000)
consecutiveFailures
number
Current count of consecutive delivery failures
circuitOpenedAt
string
ISO 8601 timestamp when circuit breaker was triggered (null if closed)
signingSecret
string
HMAC signing secret (only returned on creation, hex-encoded)

Error Scenarios

Common Patterns

Webhook Setup Flow

Health Check Automation

Best Practices

Use Descriptive Names

Name webhooks clearly (e.g., “Production ATS Sync”, “Staging Test”)

Monitor Failures

Set up alerts for consecutiveFailures > 0

Test Before Production

Always test webhooks with ping before relying on them

Secure Secrets

Use a secrets manager for signing secrets

Next Steps

Webhooks Guide

Learn about webhook payloads and signature verification

API Reference

Complete webhook endpoint documentation

Interviews

Understand interview events

Scopes

Configure webhook permissions