1eye Docs – Buyer Signals API, Webhooks, MCP & Integrations

Push buyer and company activity from your target lists to any endpoint you control — no login or authorization step required.

Before you begin

An endpoint URL that can receive POST requests
At least one Target List created (contacts or companies can be added later)
Admin or Marketer access to your 1eyeᴬᴵ workspace

For this guide, we’ll use Snowbricks as the example workspace.

Field	Example
Company	Snowbricks
Endpoint URL	https://api.snowbricks.io/hooks/mainv1
Workspace admin	Matt Bru
Admin email	matt@snowbricks.io

Configure the destination

Unlike HubSpot, Salesforce, and Slack, Webhooks doesn’t use a login step — you configure it directly at the Destination node. Step 1: Open the Destination node If the webhook isn’t configured yet, the destination shows as Not Connected until you enter an Endpoint URL and send a successful test event.

Step 2: Enter your Endpoint URL Enter the URL that should receive events.

Field	Example
Endpoint URL	https://api.snowbricks.io/hooks/mainv1

Step 3: Send a test event Select Send test event to confirm your endpoint is reachable.

✓ Test event sent successfully

Step 4: Choose Push Behavior

Option	Description
Once per Target Buyer	Push when first identified.
New Signal	Push when a new signal is received.
Every Signal	Push for every new signal.

Step 5: Add Custom Headers (optional) Add key/value headers to include with every request, such as a signing secret.

Key	Value
X-1eye-Signature	whsec_9f2a7c4b8e1d

Select + Add More to add another header.

Step 6: Save Select Save Destination. The destination updates from Not Connected to Connected.

Webhook Payload

{
  "id": "eve_354122772693041152",
  "type": "buyer.identified",
  "event_context": {
    "is_new_buyer": true,
    "is_new_signal": true,
    "is_repeat_signal": false
  },
  "data": {
    "buyer": {
      "id": "buy_348588029597872128",
      "client_id": "wor_315825016971321344",
      "contact_info": {
        "name": {
          "first": "John",
          "middle": "A",
          "last": "Doe"
        },
        "role": {
          "title": "Software Engineer",
          "function": "engineering",
          "seniority": "individual_contributor",
          "start_date": "2024-03-01"
        },
        "email": {
          "work": "john.doe@acme.ai",
          "is_valid": true
        },
        "phone": {
          "mobile": "+14155550147",
          "is_valid": true
        },
        "social": {
          "linkedin": "https://www.linkedin.com/in/johndoe",
          "twitter": "https://x.com/johndoe",
          "github": "https://github.com/johndoe",
          "facebook": "https://www.facebook.com/johndoe",
          "linkedin_followers": 1842,
          "is_linkedin_valid": true
        },
        "location": {
          "city": "San Francisco",
          "state": "California",
          "country": "United States",
          "postal_code": "94107"
        },
        "photo_url": "https://cdn.acme.ai/people/john-doe.jpg",
        "is_persona": true,
        "persona_id": "per_312309588578725888",
        "persona_name": "engineer",
        "persona_reasoning": "John is a Software Engineer on the engineering team, which matches the Engineer persona."
      },
      "company_info": {
        "name": "AcmeAI",
        "website": "acme.ai",
        "logo": "https://cdn.acme.ai/logo.png",
        "industries": [
          "artificial intelligence",
          "software",
          "information technology"
        ],
        "employee_range": "201-500",
        "founded_year": 2020,
        "annual_revenue": 50000000,
        "company_type": "private",
        "social": {
          "linkedin": "https://www.linkedin.com/company/acme-ai",
          "twitter": "https://x.com/acmeai",
          "facebook": "https://www.facebook.com/acmeai"
        },
        "location": {
          "street_address": "123 Market Street",
          "city": "San Francisco",
          "state": "California",
          "postal_code": "94105",
          "country": "United States"
        },
        "total_funding": 75000000,
        "latest_funding_stage": "series_b",
        "latest_funding_round_date": "2025-06-15",
        "is_icp": true,
        "icp_id": "icp_312301764881174528",
        "icp_name": "b2b_scaleup",
        "icp_reasoning": "AcmeAI is a B2B software company with 201-500 employees and matches the B2B Scaleup ICP."
      },
      "hems": [
        {
          "type": "md5",
          "value": "098f6bcd4621d373cade4e832627b4f6"
        },
        {
          "type": "sha256",
          "value": "9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08"
        }
      ],
      "target_lists": [
        {
          "id": "lis_348500000000000001",
          "name": "Snowflake"
        },
        {
          "id": "lis_348500000000000002",
          "name": "Enterprise AI"
        }
      ],
      "signal_count": {
        "total": 1,
        "website": 1,
        "market": 0,
        "social": 0
      },
      "first_signal_id": "sig_348588000426487809",
      "last_signal_id": "sig_348588000426487810",
      "created_at": "2026-09-03T21:32:33-07:00",
      "updated_at": "2026-09-03T21:32:38-07:00"
    },
    "signal": {
      "id": "sig_348588000426487809",
      "buyer_id": "buy_348588029597872128",
      "type": "website",
      "website": {
        "trigger": "visit",
        "url": {
          "raw": "snowbricks.io/pricing?utm_source=google&utm_medium=cpc&utm_campaign=enterprise&utm_term=data+warehouse&utm_content=pricing_ad&gclid=abc123",
          "canonical": "snowbricks.io/pricing",
          "domain": "snowbricks.io",
          "path": "/pricing"
        },
        "attribution": {
          "type": "paid",
          "source": "google_ads",
          "source_name": "Google Ads",
          "source_logo": "https://www.gstatic.com/images/branding/product/1x/ads_48dp.png"
        },
        "utm": {
          "source": "google",
          "medium": "cpc",
          "campaign": "enterprise",
          "term": "data warehouse",
          "content": "pricing_ad"
        },
        "click_ids": {
          "gclid": "abc123",
          "gbraid": null,
          "wbraid": null,
          "dclid": null,
          "li_fat_id": null,
          "msclkid": null,
          "fbclid": null,
          "ttclid": null,
          "twclid": null
        },
        "target_page": {
          "id": "tpg_348588000000000001",
          "name": "Pricing",
          "short_name": "pricing",
          "description": "Snowbricks Pricing Page"
        },
        "session": {
          "id": "ses_348588000000000001",
          "started_at": "2026-09-03T21:32:28-07:00",
          "ended_at": "2026-09-03T21:34:42-07:00",
          "duration_secs": 134
        },
        "device": {
          "browser": "chrome",
          "browser_version": "140.0",
          "os": "macos",
          "os_version": "15.6",
          "device_type": "desktop",
          "language": "en-us"
        },
        "location": {
          "ip": "203.0.113.10",
          "city": "Palo Alto",
          "state": "California",
          "country": "United States",
          "country_code": "us",
          "postal_code": "94301",
          "latitude": 37.4419,
          "longitude": -122.143,
          "timezone": "america/los_angeles"
        },
        "page": {
          "visited_at": "2026-09-03T21:32:28-07:00",
          "time_spent_secs": 120,
          "visit_count": 1,
          "first_visited_at": "2026-09-03T21:32:28-07:00",
          "last_visited_at": "2026-09-03T21:32:28-07:00",
          "total_time_spent_secs": 120
        }
      },
      "market": null,
      "social": null,
      "captured_at": "2026-09-03T21:32:28-07:00",
      "created_at": "2026-09-03T21:32:33-07:00",
      "updated_at": "2026-09-03T21:32:33-07:00"
    }
  },
  "created_at": "2026-09-03T21:37:28-07:00"
}

Monitor pushed records

From the Console, filter Webhook pushes by All / Pushed / Pending / Failed. Select a contact to see the exact payload sent to your endpoint.

Stop Webhooks

Open the workflow that uses Webhooks as a destination
Select Stop (in place of Run) on the workflow

Stopping the workflow halts all pushes to your endpoint until you run it again. Events already sent to your endpoint remain there.

Best practices

Verify your endpoint before saving Use Send test event to confirm your endpoint responds correctly before turning the destination on. Use a signing secret Add a Custom Header like X-1eye-Signature so your endpoint can verify events actually came from 1eye. Match push behavior to your use case Use Once per Target Buyer for low-volume alerting, or Every Signal for full activity streaming. Watch the Console after changes After editing your endpoint or push behavior, check the Console to confirm events are landing as Pushed, not Failed.

Troubleshooting

Issue	What to check
Send test event fails	Confirm the Endpoint URL is correct and reachable, and that your server isn’t blocking the request.
Destination shows Not Connected	Confirm the Endpoint URL is filled in and a test event has been sent successfully.
Events failing in the Console	Check your endpoint’s response — a non-2xx response is recorded as Failed.
Custom Header isn’t being sent	Confirm both the Key and Value fields are filled in before saving.

FAQ

Does Webhooks use OAuth like HubSpot or Salesforce?

No. Webhooks doesn’t require a login or authorization step — you configure it directly with an Endpoint URL and, optionally, Custom Headers.

What happens if I stop the workflow?

All pushes to your endpoint stop until you run the workflow again. Events already sent to your endpoint remain there.

Can I send to more than one endpoint?

Each Webhooks destination sends to a single Endpoint URL. To send to multiple endpoints, add a separate destination for each one.

Next step

Go to Destinations to build your first Webhooks workflow.

Get Started

Knowledge Base

Signals

Buyer Intelligence

Target Lists

Destinations

Workspace Settings

Webhooks

Before you begin

Configure the destination

Webhook Payload

Monitor pushed records

Stop Webhooks

Best practices

Troubleshooting

FAQ

Next step

​Before you begin

​Configure the destination

​Webhook Payload

​Monitor pushed records

​Stop Webhooks

​Best practices

​Troubleshooting

​FAQ

​Next step

Before you begin

Configure the destination

Webhook Payload

Monitor pushed records

Stop Webhooks

Best practices

Troubleshooting

FAQ

Next step