Boberdoo
The Boberdoo Plugin is a Taalk Certified integration that enables seamless lead distribution and call routing between Taalk’s AI Agent infrastructure and Boberdoo’s lead management platform. This plugin facilitates real-time ping/post lead transfers and voice-based engagements for insurance, finance, and service-based verticals. By capturing user data during AI Agent interactions and pushing it to Boberdoo’s API, this integration supports qualified lead delivery, campaign-based routing, and advanced decisioning logic using Boberdoo’s backend.
Use Case
Businesses using Taalk to automate lead qualification—especially in high-throughput verticals like auto insurance or extended warranty—can leverage this plugin to:
•Push fully enriched lead data captured by AI Agents into Boberdoo in real time.
•Route calls based on lead criteria (e.g., location, insurance history, credit).
•Trigger ping/post workflows or A/B test different buyer endpoints.
•Maintain compliance via LeadiD tokens and audit fields.
Endpoint
GET https://mdg.leadportal.com/new_api/api.php
Required Query Parameters
|
Parameter |
Description |
|---|---|
|
Key |
Your Boberdoo API key (keep this secure) |
|
API_Action |
Action to perform (e.g., SubmitLead) |
|
SRC_ID |
Source ID configured in Boberdoo |
|
TYPE |
Lead type (usually 9 for insurance) |
|
Unique_Identifier |
Unique ID generated by Taalk for this lead |
|
SRC |
Source alias (maps to partner, campaign, or publisher) |
|
Mode |
Must be full for complete lead delivery |
|
Sub_ID |
Sub ID used for traffic segmentation |
|
Pub_ID |
Same as SRC or specific publisher alias |
|
Origin_Phone |
Phone number captured during AI Agent interaction |
|
LeadiD_Token |
Token for compliance tracking |
|
DOB, Age, Gender, Marital_Status |
Driver demographic info |
|
Vehicle_1_Year, Make, Model, Ownership |
Vehicle info captured by Taalk |
|
Tickets_Accidents_Claims_Past_3_Years, DUI_DWI_In_The_Past_5_Years |
Risk data |
|
Credit_Rating, License_Status, Licensed_State |
Driver risk & compliance |
|
Address, City, State, ZIP |
Contact & location info |
|
|
Primary email for follow-up |
|
Current_Insurance_Company, Insured_Past_30_Days, etc. |
Coverage insights |
|
Filing_Required |
SR-22/FR-44 requirement status |
|
Additional_Drivers, Additional_Vehicles |
Household complexity |
|
Terminating_Phone |
Optional — used for call matching/tracking |
Example Request
GET https://mdg.leadportal.com/new_api/api.php?Key=abc123&API_Action=SubmitLead&SRC_ID=2001&TYPE=9&Unique_Identifier=taalk-001122&SRC=taalk_pub&Mode=full&Sub_ID=sub001&Pub_ID=taalk_pub
&Origin_Phone=14085551234&LeadiD_Token=xyz123token
&Current_Insurance_Company=Company%20Not%20Listed&DOB=01/01/1980&Age=44&
Gender=Male&Marital_Status=Single&Credit_Rating=Good&License_Status=Valid&Licensed_State=TX
&Filing_Required=No&Current_Residence=Rent&Insured_Past_30_Days=Yes&Additional_Drivers=1
&Additional_Vehicles=1
&Vehicle_1_Year=2020&Vehicle_1_Make=Toyota&Vehicle_1_Model=Camry&Vehicle_1_Ownership=Own
&Tickets_Accidents_Claims_Past_3_Years=None
&DUI_DWI_In_The_Past_5_Years=No&First_Name=John&Last_Name=Doe&Address=123+Main+St
&City=Austin&Email=john.doe@example.com&State=TX&ZIP=73301
Authentication
API Key must be passed via the Key query parameter. Ensure this is securely stored in Taalk’s plugin configuration and never exposed in frontend client calls.
Field Mapping with Taalk Variables
The following Taalk variables dynamically populate the Boberdoo request
|
oberdoo Param |
Taalk Variable |
|---|---|
|
Unique_Identifier |
<Taalk_leadID> |
|
Sub_ID |
<Taalk_Sub_ID> |
|
Pub_ID / SRC |
<Taalk_SRC> |
|
Origin_Phone |
<contact.phone> |
|
Current_Insurance_Company_Months |
<Taalk_Driver_1_Current_Insurance_Company_Months> |
|
Bodily_Injury_Limits |
bi_output_categories:no body injury |
|
LeadiD_Token |
<Taalk_LeadiD_Token> |
|
Current_Insurance_Company |
agency_name:Company Not Listed |
|
DOB |
<Taalk_Driver_1_Birthdate> |
|
Age |
<Taalk_Driver_1_Age:50> |
|
Gender |
<Taalk_Driver_1_Gender> |
|
Marital_Status |
<Taalk_Driver_1_Marital_Status:Single> |
|
Credit_Rating |
<Taalk_Driver_1_Credit_Rating:Good> |
|
License_Status |
<Taalk_Driver_1_License_Status> |
|
Licensed_State |
<Taalk_Driver_1_Licensed_State> |
|
Filing_Required |
<Taalk_Driver_1_Filing_Required> |
|
Current_Residence |
restrict_rent_status:Rent |
|
Insured_Past_30_Days |
<Taalk_Driver_1_Insured_Past_30_Days> |
|
Additional_Drivers |
<Taalk_Driver_1_Additional_Drivers> |
|
Additional_Vehicles |
<Taalk_Driver_1_Additional_Vehicles> |
|
Vehicle_1_Year/Make/Model |
<Taalk_Vehicle_1_Year/Make/Model> |
|
Vehicle_1_Ownership |
<Taalk_Ownership> |
|
Tickets_Accidents_Claims_Past_3_Years |
<Taalk_Driver_1_Tickets_Accidents_Claims_Past_3_Years> |
|
DUI_DWI_In_The_Past_5_Years |
<Taalk_Driver_1_DUI_DWI_In_The_Past_5_Years> |
|
First_Name |
<firstName> |
|
Last_Name |
<lastName> |
|
Address |
`correct_address |
|
City |
<Taalk_Driver_1_City> |
|
|
<Taalk_Driver_1_Email> |
|
State |
<Taalk_Driver_1_State> |
|
ZIP |
<Taalk_Driver_1_Zip> |
Response Handling
Typical responses from Boberdoo include success status and lead delivery ID, or error messages if data is incomplete or misformatted.
Success
{
"status": "success",
"lead_id": "BBD-88332"
}Failure
{
"status": "error",
"message": "Missing DOB or invalid age"
}
Best Practices
•Always validate core fields like DOB, ZIP, and LeadiD before submitting.
•Use fallback values with clear defaults to avoid incomplete submissions.
•Monitor submission logs and response codes in your Taalk dashboard.
•Secure the API key and ensure all API calls originate from the backend.
Support
For integration support, contact your Taalk Implementation Specialist or support@taalk.ai. For endpoint schema changes, refer to Boberdoo’s API Docs.