Integrations

SharpSpring Webhooks and Form Postbacks

SharpSpring can post captured form data to a third-party Postback URL. FastHook turns that postback into an inspectable, routable event stream.

Capture the original request first, enforce the available trust boundary, then route and replay from durable evidence.

How the integration works

  • The strongest documented use case is a form Postback URL rather than a broad signed event-subscription API.
  • FastHook accepts the POST and preserves the original lead fields for mapping.
  • A secret query value protects the public receiver when the sender cannot add a signature header.
  • The secret query field is removed before request metadata is stored.

Create the FastHook source

Create SHARPSPRING source
curl -X POST "https://api.fasthook.io/v1/sources" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "SharpSpring Webhooks and Form Postbacks",
    "type": "SHARPSPRING",
    "config": {
      "auth_type": "PROVIDER_SIGNATURE",
      "auth": {
        "provider": "SHARPSPRING",
        "webhook_signing_secret": "long-random-url-secret",
        "query_parameter_name": "secret"
      },
      "allowed_http_methods": ["POST"]
    }
  }'

Append ?secret=YOUR_SECRET to the generated Source URL before saving it in the provider.

Setup

  1. Create a SHARPSPRING source and choose a URL secret.
  2. Append ?secret=YOUR_SECRET to the FastHook Source URL.
  3. Use the complete URL as the SharpSpring form Postback URL.
  4. Submit a test lead, inspect its exact field names, and add transformations before delivery.

Production notes

  • Do not describe form postbacks as a general signed SharpSpring event API.
  • Treat email addresses, phone numbers, and form answers as personal data.
  • Keep mappings tolerant of optional and custom form fields.

Related documentation