Account Signal Agent Webhook

The Account Signal Webhook delivers the most relevant signals for your target accounts in near real time. Each notification includes a concise summary and context on how it can help your product or service, enabling immediate action and automated workflows.

Register Your Webhook

To receive Account Signal events, you must register a webhook endpoint where notifications will be delivered.


  1. Create an Endpoint

    Set up an HTTPS endpoint in your application that can accept POST requests and process JSON payloads.

    Requirements

  • Must support HTTPS
  • Must accept POST requests

  1. Register the Endpoint

    To start receiving Account Signal events, you must register your webhook endpoint with our team.

    Send a request to our support team at [email protected] with the following details:

  • Organization Name

  • Webhook endpoint URL (HTTPS)

  • Agent Name

    Our team will review your request, configure the webhook, and share a confirmation once it is activated.


Webhook Delivery

The Account Signal Agent Webhook delivers events to your registered endpoint in near real time using HTTP POST requests.

Delivery Method

  • Protocol: HTTPS
  • Method: POST
  • Content-Type: application/json
  • Payload Format: JSON

Response Parameters

Response ParameterValue TypeDescription
recordIdStringUnique ID provided by the user, echoed in the response to link input and output.
compGUIDStringSMARTe unique company identifier.
compNameStringName of the company.
compWebsiteStringWebsite of the company.
totalPagesNumberTotal number of pages available for the result set.
totalCountNumberTotal number of records available across all pages.
pageNoNumberCurrent page number of the response.
pageSizeNumberNumber of results returned per page.
transactionIdStringUnique ID for this transaction/request.
signalsListObject containing the identified account signals
signalIdStringA unique identifier for the signal.
titleStringA short, human-readable headline representing the signal.
descriptionStringA concise summary of the signal, including context on why it matters and how it can help your product or service.
categoryStringThe broad classification of the signal, indicating the type or theme it belongs to (for example: expansion, funding, leadership change, partnership, etc.)
sourceUrlStringThe original source URL from which the signal was derived.
timestampStringThe date and time when the signal was generated

What’s Next