Property Leads (Co-reg Only)

The Property Leads (Co-reg only) Leads endpoint allow you as a Publisher to post Property Leads (Co-reg only) leads directly to Bright Horizons Media. Leads sent to the API use the POST method and require both credentials and your Publisher to be enabled for posting leads. Leads are posted in JSON format.

This endpoint is only intended for Property Leads (Co-reg only) Leads generated through co-reg paths.

Targeting: Nationwide, homeowners, ages 21+. TCPA Disclaimer: By clicking YES, I provide my signature expressly consenting to receive autodialed and or artificial/prerecorded voice marketing calls and texts from Sell My House Fast or its subsidiaries, affiliates, or agents on the phone number provided. I understand that I will receive these calls and texts even if I am on a federal or state do not call registry. I understand that I can revoke this consent at any time. I understand that my consent is not a condition of any purchase. I CONFIRM that all of my information is accurate and consent to be called and texted as provided above.

Method	Endpoint	Endpoint Type
Post	https://api.brighthorizonsmedia.com/post/property-leads/coreg/	JSON

POST PARAMETERS

To successfully post Property Leads (Co-reg Only) leads, two arrays need to be passed to the JSON endpoint: the xauth[] array and the transaction[] array.

The xauth[] array contains your Publisher ID and the API key assigned by your Account Manager.

The transaction[] contains all the details about the lead (first name, last name, email, consumer IP, etc.).

xauth[] Parameters

Field	Type	Required?	Description
affiliateid	INT	Yes	Your Publisher Id (aka Affiliate Id) provided by your Account Manager
key	STRING (36)	Yes	The API Key provided by your Account Manager.

transaction[] Parameters

Field	Type	Required	Description
firstname	STRING	Yes	First name as provided by the consumer
lastname	STRING	Yes	Last name as provided by the consumer
dob	STRING	Yes	Date of birth as provide by the consumer. Must be in the format YYYY-MM-DD.
gender	STRING	Yes	The gender as provided by the consumer. Must be either "male" or "female".
phone	STRING	Yes	Phone number as provided by the consumer. Can be passed in any format (see following examples) but must be a valid phone number with 10 digits. Examples: 3105551212, (310) 555-1212, 310-555-1212, 310.555.1212.
email	STRING	Yes	Email address as provided by the consumer
address	STRING	Yes	Street address as provided by the consumer
address2	STRING	Optional	Street address as provided by the consumer
city	STRING	Yes	City as provided by the consumer. If not provided, we will map the city based on the zip code provided.
state	CHAR (2)	Yes	The state abbreviation as provided by the consumer. If not provided, we will map the state based on the zip code provided.
zip	STRING	Yes	The zip code as provided by the consumer. For US zip codes, make sure to include any leading zeros to ensure the zip code has a length of 5 characters.
ip	STRING	Yes	The IP address of the consumer when the form was submitted on your website (not your server IP address). Can be either IPV4 or IPv6.
source	STRING	Yes	The fully qualified URL (or domain) of the webpage where the lead was generated (excluding any query string parameters)
trustedformcertid	STRING	Yes	The TrustedForm URL
sub1	STRING	Yes	Additional field for tracking purposes
sub2	STRING	Optional	Additional field for tracking purposes
sub3	STRING	Optional	Additional field for tracking purposes
sub4	STRING	Optional	Additional field for tracking purposes
sub5	STRING	Optional	Additional field for tracking purposes

REQUESTS & RESPONSES

SAMPLE REQUEST

POST /post/property-leads/coreg/ HTTP/1.1
Host: https://api.brighthorizonsmedia.com
Content-Type: application/json; charset=utf-8
Content-Length: 519

{
    "xauth":
    {
        "affiliateid": 123456,
        "key": "zzzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzzzz"
    },
    "transaction":
    {
        "firstname": "JJ",
        "lastname": "McClure",
        "phone": "7025551212",
        "email": "jjmcclure@example.com",
        "address": "123 Cannonball Lane",
        "address2": "Apt 3",
        "city": "Boulder City",
        "state": "NV",
        "zip": "89002",
        "gender": "male",
        "dob": "1989-10-11",
        "ip": "192.168.168.1",
        "source": "yourdomain.com",
        "trustedformcertid": "https://cert.trustedform.com/ZZZWW8ba26XX85bXX16d3cb6c44cc30a7da48ba1",       
        "sub1": "your sub id",
        "sub2": "",
        "sub3": "",
        "sub4": "",
        "sub5": ""        
    }
}

SAMPLE RESPONSE

When a Property Leads (Co-Reg Only) lead is posted to us, a JSON response will be returned containing useful information about whether the lead was accepted and any additional information we can provide. Below is an example of a successful response.

A response with sold = 1 (or "sold":1) means the lead was accepted by a buyer and is billable. Sold = 0 (or "sold":0) is NOT billable.

The "accepted" parameter is not to be used for determining whether a lead is billable.

{
    "validated": 1,
    "accepted": 1,
    "sold": 1,
    "disposition": "SOLD",
    "messages": [],
    "errors": [],    
    "transactionid": 123456789,
    "leadid": 123456789
}

FAILED RESPONSE

If the request failed, the response will include an errors object which may contain 1 or more messages/errors. This example will return an errors because the dateofbirth value was not passed. Reminder, we do not log or record leads in our system that could not be validated.

{
    "validated": 0,
    "accepted": 0,
    "sold": 0,
    "disposition": ,
    "messages": [
        "Property Lead could not be validated"
    ],
    "errors":
    [
        [
            "Date of Birth (required): can not be empty"
        ]
    ]
}