Ping & Post API

Posting Instructions Fields Required Ping API Post One Step System
Health Ins. Home Ins. Legal Auto Ins. Home Services Life ins. Finance / Debt.
Calls
Call Home services Call Auto Ins. Call Health Ins. Call Legal. Call Finance/Debt.

Ping & Post Instructions
for Call Routing Auto Insurance

Let's Make A Lead API
Please use the following instructions to use our Ping/Post or Direct Post system for Call Routing Auto Insurance Vertical.
In order to get identified, you will need to send the following parameters:
Ping
Required 		Post
Required 		field Contents Example of value
YES YES partnerid Will be provided XYZ
YES YES key Will be provided 771f5924706521c73464341fc48afb05
YES YES numcategory 12003 - Call Routing Auto Insurance   
12003
YES YES subid Your sub Source 123
OPTION OPTION resptype 'XML' to receive an XML response.
'JSON' to receive an JSON response.
if empty, the response format will be by default. 		XML
YES price The payout for the lead in $.
 0.15
NO OPTION price_tag 1 to receive the Price inside the Post response.
if empty, the response format will be by default. (See response example)		 1
NO YES token Value you received in case of positive Ping.
Must be sent on the Post.		 e69412030cc93b47cf5be6f7e3ee998c
Fields Required for Call Routing Auto Insurance
Ping
Required 		Post
Required 		fieldname Value - Label Example of value
YES YES transfer_type integer Set. Allowed values:
1 - Inbounds
2 - Transfers
1
YES YES zipcode varchar(5) 33139
NO NO ip varchar(50) 10.0.0.1
NO NO shared
complementary datas are requireds if shared is sent and ≠ 0
display complementary datas
 1 (Yes) 0
NO NO universal_leadid varchar(50) FFEA9CB6-1A2D-9DA3-0188-96A93D26875C
NO NO trusted_form_token 544fa56524d00e3a0cb321b988fc40d8c42c7160
NO NO requested_policy_coverage_type integer 1
NO NO requested_policy_property_damage integer 10000
NO NO requested_policy_bodily_injury integer 1
NO NO current_policy_insurance_company
complementary datas are requireds if current_policy_insurance_company is sent and ≠ 0
display complementary datas
 integer
Please, Send 0 if Not Insured
 		0
NO NO driver1
complementary datas are requireds if driver1 is sent and ≠ 0
display complementary datas
 integer 1
NO NO driver2
complementary datas are requireds if driver2 is sent and ≠ 0
display complementary datas
 integer 0
NO NO driver3
complementary datas are requireds if driver3 is sent and ≠ 0
display complementary datas
 integer 0
NO NO vehicle1
complementary datas are requireds if vehicle1 is sent and ≠ 0
display complementary datas
 integer 1
NO NO vehicle2
complementary datas are requireds if vehicle2 is sent and ≠ 0
display complementary datas
 integer 0
NO NO vehicle3
complementary datas are requireds if vehicle3 is sent and ≠ 0
display complementary datas
 integer 0
NO NO firstname varchar(50) John
NO NO lastname varchar(50) Doe
NO NO state varchar(2) FL
NO NO email varchar(255) johndoe@gmail.fr
NO NO telephone varchar(10) 8772681223
NO NO telephone2 varchar(10) 8772681223
NO NO address varchar(255) 1210 Ocean Drive
NO NO address2 varchar(255) suite #1002
NO NO city varchar(50) Miami
NO NO comment varchar(500) Your Comment here
NO NO tcpa_optin 1 (Yes) or 2 (No) 1
NO NO phone_last_four varchar(4) 2369
NO NO trusted_form_available 1 (Yes) 0
NO NO universal_leadid_available 1 (Yes) 0
OPTION OPTION 1to1consent 0 (No), 1 (Yes). 0 by default 0
PING API
Methods
You can call the PING API using three different methods:
  • cURL POST with URL-encoded data
  • cURL POST with JSON data
  • HTTP GET request

    Required Fields
    When making a PING request, the following fields are mandatory and must be included:
  • partnerid: Your unique partner ID.
  • key: Your API key for authentication.
  • numcategory: The category number for the service.
  • subid: Your unique sub ID.

    • In addition to the fields mentioned above, all fields marked as "Ping Required" with Yes in the "Fields Required" table above must also be included in the request.

    Response
    The API will respond in one of the following ways:
  • Accepted: We will return a price and a token that you can reuse in the POST API. For call routing, you also receive a call duration linked to the price (the minimum duration required to validate the call).
  • Rejected: The request will be rejected with a detailed reason provided in the response.
    TEST MODE
    Only For test Mode please :
  • use key = test_mode (The Live Mode Key will be provided upon completion of successful Test.)
  • use subid = match To simulate a positive response
    • For direct post according to a ziplist
  • add price = 0.5
    • #errorCode# Meaning
    1000 Server under maintenance
    1100 Request limit exceeded
    2000 Invalid Partner ID or Blocked source
    3000 Approval Phase
    4000 Daily Cap reached
    5000 No coverage or buyers
    6000 Minimum bid not met
    Other Ask Your Representative
    POST API
    Required Fields
    When making a POST request, the following fields are mandatory and must be included:
  • partnerid: Your unique partner ID.
  • key: Your API key for authentication.
  • numcategory: The category number for the service.
  • subid: Your unique sub ID.
  • token: the token received on the Ping response.

    • In addition to the fields mentioned above, all fields marked as "Post Required" with Yes in the "Fields Required" table above must also be included in the request.

    Response
    The post API will respond in one of the following ways:
  • Accepted:
    PhoneNumber received on post response
    The call have to be forwarded to the provided PhoneNumber in the next 30 seconds
  • Rejected: if the leads is post rejected, .
    • ONE STEP SYSTEM
    The One-Step Method is a quick and easy way to get a phone number to transfer a call.

    By using the API endpoint http://call.letsmakealead.com/Ping_Partner_CR.php, you will receive all the necessary details in one step.

    Along with the offer and call duration, the response will include the phone number to transfer the call immediately if the offer is accepted.

    This saves time and simplifies the process.

    jerems14