Debt Leads (Co-reg Only)
The Debt Leads endpoint allow you as a Publisher to post Debt 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 Debt Leads generated through co-reg paths.
Hours: 9am-9pm EST Mon-Fri. Excluded states: CO, ND, OR, VT, WV, WY. Must be employed. Ad copy must be approved before going live. Marketing partners list: Synergy Debt, Credit Card Help Desk, Americor, Level33, Infinity Client Solutions
Language for FCRA Campaign (speak to your Account Manager): By clicking on the “[CTA button name here]” button above, I am providing express written consent under the Fair Credit Reporting Act for Americor and its partners to obtain my consumer credit report from my credit profile or other information from a Credit Bureau(s) in order to provide me with personal loan and debt consolidation options without affecting my credit score.
| Method | Endpoint | Endpoint Type |
|---|---|---|
| Post | https://api.brighthorizonsmedia.com/post/debt/ | JSON |
POST PARAMETERS
To successfully post Debt 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. |
| 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. |
| 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. |
| finances | ARRAY | Yes |
The finances parameter is an array containing key => value pairs of data related to the consumer's finances. All fields are required. unsecureddebtamount (INTEGER) - the estimated unsecured debt value as provided by consumer (example: 14750) |
| 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/debt/ HTTP/1.1
Host: https://api.brighthorizonsmedia.com
Content-Type: application/json; charset=utf-8
Content-Length: 525
{
"xauth":
{
"affiliateid": 123456,
"key": "8526df83-yy6u-fg7k-3d4f-3d4b9m2z3bb9"
},
"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",
"finances":
{
"unsecureddebtamount": 14500
},
"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 Debt 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 unsecureddebtamount 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": [
"Debt Lead could not be validated"
],
"errors":
[
[
"Unsecured Debt Amount (required): can not be empty and must INT"
]
]
}