Skip to main content
All CollectionsAdvanced Topics
Webhooks in MetaLocator
Webhooks in MetaLocator

MetaLocator can trigger events when certain actions occur to push data to external systems

Michael Fatica avatar
Written by Michael Fatica
Updated over 4 months ago

Webhooks are requests to 3rd party HTTP endpoints that are configured to listen for GET and POST requests containing information about an event that has occurred in MetaLocator.

This feature is available to Enterprise users only.

MetaLocator staff can configure Webhooks for the following events:

  1. Where to Buy eCommerce Transaction

  2. Lead Submittal

  3. Single (non-bulk) Location Data Update via Crowdsourcing or the dashboard.

The Webhook URL must be HTTPS and must be submitted to the helpdesk for evaluation, penetration testing and approval.

Lead Webhooks

Lead Webhook Payload includes the lead and the target location object. Webhooks should be secured to ensure the validity of the posted object. The actual posted schema will vary to include any customer-configured custom fields:

Sample Payload shown below

{
"lead": {
"id": "1234",
"subject": "New Lead",
"body": "<!DOCTYPE html>....</html>\n",
"name": "Name",
"from": "sample@leadexample.com",
"to": "recipient@customer.com",
"message": "Message body",
"cc": null,
"received": "2022-03-21 19:57:04",
"custom1": "Red",
"custom2": "1",
"custom3": null,
"custom4": null,
"custom5": null,
"custom6": null,
"custom7": null,
"custom8": null,
"custom9": null,
"custom10": null,
"custom11": null,
"custom12": null,
"custom13": null,
"custom14": null,
"custom15": null,
"custom16": null,
"custom17": null,
"custom18": null,
"custom19": null,
"custom20": null,
"custom21": null,
"custom22": null,
"custom23": null,
"custom24": null,
"custom25": null,
"custom26": null,
"custom27": null,
"custom28": null,
"custom29": null,
"custom30": null,
"custom31": null,
"custom32": null,
"custom33": null,
"custom34": null,
"custom35": null,
"custom36": null,
"custom37": null,
"custom38": null,
"custom39": null,
"custom40": null,
"location_id": "1",
"visitor_id": null,
"item_id": "123456",
"action": null,
"diagnosticcode": null,
"mltable": "locations",
"viewed": null,
"followup_flag": "0",
"token_hash": "caaaaabbbbcccccdddddeeeefffffgggg123456",
"sender_ipaddr": "172.28.128.1",
"spam_action": "",
"expired": "0",
"reminder": "0",
"reminder_flag": null,
"budget": "0",
"currency": "",
"budgetusd": null,
"unsubscribed": "0",
"fromphone": "",
"utm_source": "",
"utm_medium": "",
"utm_campaign": "",
"utm_content": "",
"utm_keyword": "",
"http_status_code": "200",
"webhook_response": "",
"status_id": null,
"revenue": null,
"revenue_currency": null,
"revenue_usd": null,
"reason_id": null
},
"location": {
"id": "1",
"name": "Sample Location",
"type": "",
"description": "Sample Record.",
"published": "1",
"user_id": "0",
"isdirty": "1",
"geofailed": "0",
"address": "1234 Sample Way",
"address2": null,
"city": "Milwaukee",
"state": "WI",
"county": null,
"postalcode": "53202",
"country": "United States",
"date": null,
"startdate": null,
"enddate": null,
"phone": "123-123-4032",
"hours": null,
"fax": null,
"link": "https://google.com",
"online": null,
"tld": "US",
"gallery": null,
"metadescription": null,
"metakeywords": null,
"language": null,
"sourcefile": "starter import (1).csv",
"staticlink": null,
"lng": null,
"lat": null,
"publishstart": null,
"publishend": null,
"mlwppostid": null,
"reviewmonitoringenabled": "0",
"factualenabled": "0",
"slug": "",
"retailers_id": null,
"tagmasksum": "0",
"locale": null,
"datecreated": "2024-08-19 16:26:34",
"dateupdated": null
}
}

Request field content

eCommerce Transaction

Location Data Update

Location data schema may change on a per-account basis as additional fields are added by the customer.

Did this answer your question?