De-Dupe (duplication rules) are DISABLED.
Validation services are NOT ENABLED.
https://helpcentre.leadbyte.co.uk/api/submit.php?campid=TEST&sid=1&returnjson=yes
You can submit leads using either "GET" or "POST" methods, however "POST" is recommended.
HTTP/HTTPS Accepted.
Example Post String:
https://helpcentre.leadbyte.co.uk/api/submit.php?returnjson=yes&campid=TEST&sid=1&email=leadbyte@aol.com&firstname=David&lastname=Beckham&street1=Hope Street&country=United Kingdom&phone1=07879000194
URL ENCODING NOTICE
Please URL Encode your HTTP Data Submissions. Since URLs often contain characters outside the ASCII set,
the URL has to be converted into a valid ASCII format. URL encoding replaces unsafe ASCII characters with a "%" followed by two hexadecimal digits. URLs cannot contain spaces.
URL encoding normally replaces a space with a + sign.
We return a JSON response as follows.
{
"code": 1,
"response": "OK",
"info": [],
"leadId": 123456,
"processTime": 0.12,
"timestamp": "YYYY-MM-DDTHH:MM:SSZ"
}
Any code other than 1 should be regarded a failed submission. Response codes are descriptive so a reason for failure shall be returned.
Example of rejection:
{
"code": -8,
"response": "HLR rejection",
"info": {
"status": "UNDELIV",
"code": "EC_UNKNOWN_SUBSCRIBER"
},
"leadId": null,
"processTime": 0.77,
"timestamp": "2016-03-17T11:53:39Z"
}
Response Codes:
-2: Duplicate or resubmission
-3: Remote system error
-4: Campaign cap reached
-5: Validation error
-7: Supplier not authorised
-8: HLR rejection
-9: Campaign not active
-10: PAF rejection
-11: IP address blocked
-12: Email rejection
-13: Landline rejection
-14: IP address country rejection
-15: Number matched TPS database
-16: Number matched DNCR database
-100: Internal error
Please note that live responses are compressed onto a single line. If you wish to beautify the JSON for readability, please use this tool:
http://codebeautify.org/jsonviewer
This is a test campaign and any notes for your supplier will appear here.
This guide has been produced by your account manager LeadByte Team (leadbyteteam) on behalf of LeadByte.
If you have any questions then please do not hesitate to get in touch.