- 04 Jan 2024
- 17 Minutes to read
- Print
- DarkLight
Jornaya Intelligence API
- Updated on 04 Jan 2024
- 17 Minutes to read
- Print
- DarkLight
Introduction
Jornaya Intelligence is a REST API call that relies on a unique LeadiD token that is generated by our javascript snippet to witness the consumer's experience as they move through a lead funnel. The responses in this request are derived data insights gathered from the lead event.
Example Request Structure (GET method)
https://api.leadid.com/SingleQuery?lac={ACCOUNTCODE}&id={LEADIDTOKEN}&lak={AUDITKEY}&lpc={PROVIDERCODE}&data={DATA}
Parameter Definitions
Name | Value | Required | Description |
URL | https://api.leadid.com/SingleQuery? | Yes | The URL to be used for the query. |
Method | GET or POST | Yes | The HTTPS method to be used. |
lac | xxxxxxxx-xxxx-xxxx-xxxx | Yes | Your Jornaya Account Code. |
id | 36 Character LeadiD token | Yes | The LeadiD token. |
lak | xxxxxxxx-xxxx-xxxx-xxxx | Yes | The Audit Key for this query. |
lpc | Alphanumeric string | Yes | A value that identifies the Provider from whom you received this lead. |
data | Pipe | Separated Data with field data labels delimited by semicolons. e.g., email;joe@smith.com|f_name;joe | Yes | The data for which you want to determine Data Integrity. Note: a list of Data Integrity Field Data Labels can be found at the end of this document. |
recordid | Integer or string | When applicable | This is the Lead Management System’s or destination system’s unique identifier for the specific lead record. |
format | json, xml | No | The format in which you would like the data returned. The default value is JSON. |
agency | xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx | When applicable | The agency parameter allows a company that is an AOR or LMS for a client to perform queries on behalf of that client and identify itself accordingly by passing in its own Account Code. |
Security for Usage
The usage of HTTPS/TLS is highly recommended when implementing the Jornaya TCPA Guardian (3rd Party) API. This ensures data transmitted between your networks and Jornaya’s systems are securely encrypted and protected. Jornaya supports the usage and configuration of TLS 1.2, and the following TLS cipher suites:
ECDHE-ECDSA-AES128-GCM-SHA256 | ECDHE-RSA-AES256-SHA384 |
ECDHE-RSA-AES128-GCM-SHA256 | ECDHE-RSA-AES256-SHA |
ECDHE-ECDSA-AES128-SHA256 | ECDHE-ECDSA-AES256-SHA |
ECDHE-RSA-AES128-SHA256 | AES128-GCM-SHA256 |
ECDHE-ECDSA-AES128-SHA | AES128-SHA256 |
ECDHE-RSA-AES128-SHA | AES128-SHA |
ECDHE-ECDSA-AES256-GCM-SHA384 | AES256-GCM-SHA384 |
ECDHE-RSA-AES256-GCM-SHA384 | AES256-SHA256 |
ECDHE-ECDSA-AES256-SHA384 |
At any future time, Jornaya may revise the list of supported TLS protocols and cipher suites as required by industry security best practices. You will be notified in advance of such changes to ensure continued successful operations of your integrations with Jornaya’s services.
Example Response Structure
JSON | XML |
---|---|
{ | <audit> |
"audit": { | <token>{LeadiD}</token> |
"token": "{LeadiD}", | <data_integrity>0</data_integrity> |
"data_integrity": 0, | <device_five_minutes>0</device_five_minutes> |
"device_five_minutes": 0, | <device_hour>0</device_hour> |
"device_hour": 0, | <device_twelve_hours>0</device_twelve_hours> |
"device_twelve_hours": 0, | <device_day>0</device_day> |
"device_day": 0, | <device_week>0</device_week> |
"device_week": 0, | <ip_five_minutes>0</ip_five_minutes> |
"ip_five_minutes": 0, | <ip_hour>0</ip_hour> |
"ip_hour": 0, | <ip_twelve_hours>0</ip_twelve_hours> |
"ip_twelve_hours": 0, | <ip_day>0</ip_day> |
"ip_day": 0, | <ip_week>0</ip_week> |
"ip_week": 0, | <consumer_five_minutes>0</consumer_five_minutes> |
"consumer_five_minutes": 0, | <consumer_hour>0</consumer_hour> |
"consumer_hour": 0, | <consumer_twelve_hours>0</consumer_twelve_hours> |
"consumer_twelve_hours": 0, | <consumer_day>0</consumer_day> |
"consumer_day": 0, | <consumer_week>0</consumer_week> |
"consumer_week": 0, | <lead_five_minutes>1</lead_five_minutes> |
"lead_five_minutes": 1, | <lead_hour>1</lead_hour> |
"lead_hour": 1, | <lead_twelve_hours>1</lead_twelve_hours> |
"lead_twelve_hours": 1, | <lead_day>1</lead_day> |
"lead_day": 1, | <lead_week>1</lead_week> |
"lead_week": 1, | <total_entities>1</total_entities> |
"total_entities": 1, | <total_hops>1</total_hops> |
"total_hops": 1, | <lead_dupe_check>01</lead_dupe_check> |
"lead_dupe_check": "01", | <consumer_dupe_check>00</consumer_dupe_check> |
"consumer_dupe_check": "00", | <authentic>1</authentic> |
"authentic": 1, | <reg_rule>1</reg_rule> |
"reg_rule": 1, | <age>08</age> |
"age": "08", | <age_rule>2</age_rule> |
"age_rule": 2, | <duration>05</duration> |
"duration": "05", | <duration_rule>1</duration_rule> |
"duration_rule": 1, | <data_integrity_rule>3</data_integrity_rule> |
"data_integrity_rule": 3, | <data_integrity_passed> |
"data_integrity_passed": | <item>Firstname</item> |
[ | <item>Data</item> |
"Firstname", | <item>correct</item> |
"Data", | </data_integrity_passed> |
"correct" | <data_integrity_failed> |
], | <item>something</item> |
"data_integrity_failed": | <item>other</item> |
[ | <item>this</item> |
"something", | <item>test@email.com</item> |
"other", | </data_integrity_failed> |
"this", | <url_rule>1</url_rule> |
"test@email.com" | <url_value>0</url_value> |
], | <entity_rule>1</entity_rule> |
"url_rule": 1, | <entity_value>0</entity_value> |
"url_value": 0, | <device_five_minutes_rule>1</device_five_minutes_rule> |
"entity_rule": 1, | <device_hour_rule>1</device_hour_rule> |
"entity_value": 0, | <device_twelve_hours_rule>1</device_twelve_hours_rule> |
"device_five_minutes_rule": 1, | <device_day_rule>1</device_day_rule> |
"device_hour_rule": 1, | <device_week_rule>1</device_week_rule> |
"device_twelve_hours_rule": 1, | <ip_five_minutes_rule>1</ip_five_minutes_rule> |
"device_day_rule": 1, | <device_hour_rule>1</device_hour_rule> |
"device_week_rule": 1, | <device_twelve_hours_rule>1</device_twelve_hours_rule> |
"ip_five_minutes_rule": 1, | <device_day_rule>1</device_day_rule> |
"ip_hour_rule": 1, | <device_week_rule>1</device_week_rule> |
"ip_twelve_hours_rule": 1, | <ip_five_minutes_rule>1</ip_five_minutes_rule> |
"ip_day_rule": 1, | <ip_hour_rule>1</ip_hour_rule> |
"ip_week_rule": 1, | <ip_twelve_hours_rule>1</ip_twelve_hours_rule> |
"lead_five_minutes_rule": 1, | <ip_day_rule>1</ip_day_rule> |
"lead_hour_rule": 1, | <ip_week_rule>1</ip_week_rule> |
"lead_twelve_hours_rule": 1, | <lead_five_minutes_rule>1</lead_five_minutes_rule> |
"lead_day_rule": 1, | <lead_hour_rule>1</lead_hour_rule> |
"lead_week_rule": 1, | <lead_twelve_hours_rule>1</lead_twelve_hours_rule> |
"consumer_five_minutes_rule": 1, | <lead_day_rule>1</lead_day_rule> |
"consumer_hour_rule": 1, | <lead_week_rule>1</lead_week_rule> |
"consumer_twelve_hours_rule": 1, | <consumer_five_minutes_rule>1</consumer_five_minutes_rule> |
"consumer_day_rule": 1, | <consumer_hour_rule>1</consumer_hour_rule> |
"consumer_week_rule": 1, | <consumer_twelve_hours_rule>1</consumer_twelve_hours_rule> |
"total_entities_rule": 1, | <consumer_day_rule>1</consumer_day_rule> |
"total_hops_rule": 1, | <consumer_week_rule>1</consumer_week_rule> |
"lead_dupe_check_rule": 3, | <total_entities_rule>1</total_entities_rule> |
"consumer_dupe_check_rule": 1, | <total_hops_rule>1</total_hops_rule> |
"lead_duration": 80, | <lead_dupe_check_rule>3</lead_dupe_check_rule> |
"lead_age": 116.91330003738, | <consumer_dupe_check_rule>1</consumer_dupe_check_rule> |
"result":3 | <lead_duration>80</lead_duration> |
} | <lead_age>116.91330003738</lead_age> |
<result>3</result> | |
</audit> |
Data Responses
The following sections list the responses (and associated values) received when employing Jornaya Intelligence during a lead audit.
Basic
Audit | ||
---|---|---|
Data Point | Value | Description |
token | {LeadiD token} | The LeadiD token being returned |
blocked value | -1 | If the value returned in any section is -1, then the data values for that section have been blocked by the creator's campaign. This does not prevent the associated action flags from being returned. Configuring a campaign in this manner allows the creator to return action flags without sharing specific numeric data. |
Authentic | ||
---|---|---|
Data Point | Value | Description |
authentic | 0 | One or more of the conditions have been met below and no additional data will be returned for this LeadiD token:
|
1 | Authentic LeadiD |
Lead Age | ||
---|---|---|
Data Point | Value | Description |
lead_age | ## | The number of seconds old the lead is |
00 | < 5 minutes old | |
01 | 5 - 30 minutes old | |
02 | 30 - 60 minutes old | |
03 | 1 - 4 hours old | |
04 | 4 - 12 hours old | |
05 | 12 - 24 hours old | |
06 | 1 - 2 days old | |
07 | 2 days - 1 week old | |
08 | 1 week - 1 month old | |
09 | 1 month - 1 year old | |
10 | > 1 year old |
Lead Duration | ||
---|---|---|
Data Point | Value | Description |
lead_duration | ## | The number of seconds the consumer was on the form |
00 | Duration Not Available | |
01 | Consumer Spent < 5 seconds on the form | |
02 | Consumer Spent 5-30 seconds on the form. | |
03 | Consumer Spent 30-60 seconds on the form | |
04 | Consumer Spent 1-5 minutes on the form | |
05 | Consumer Spent 5-30 minutes on the form | |
06 | Consumer Spent 30-60 minutes on the form | |
07 | Consumer Spent > 1 Hour on the form |
Data Integrity | ||
---|---|---|
Data Point | Value | Description |
NOTE: Device data points will only be returned for LeadiD tokens generated by a Web campaign script. | ||
data_integrity | 0 | Mismatch: The value provided was not matched to any data witnessed by Jornaya during the lead event. |
1 | Match: The value of the data you submitted IS what was actually entered on the lead form. | |
2 | Mismatch With Disclosure: The value of the data you submitted is NOT what was actually entered but may have been changed by the generator. | |
3 | Default Value: The data sent was the default field value. | |
fields | array | Elements, where the key is the field name and the value, is the data_integrity value/outcome (see above). NOTE Email integrity is checked in 3 parts. The complete email is checked. In the event that there is not a match on the complete email address, the data_integrity results for each of these components are also returned in the response. |
data_integrity_failed | array | Array list of data submitted that failed data integrity. |
data_integrity_passed | array | Array list of data submitted that passed data integrity. |
data_integrity_default | array | Array list of data submitted that was the default values. |
Lead Origin | ||
---|---|---|
Data Point | Value | Description |
url_value | 0 | No URLs were matched in your URL flag list. |
1 | One or more URLs were matched in your URL flag list. | |
entity_value | 0 | No Entities were matched in your entity flag list. |
1 | One or more Entities were matched in your entity flag list. |
Consumer Origin | ||
---|---|---|
Data Point | Value | Description |
call_center | 1 | Information was entered by a 3rd party. NOTE: This data point is only returned when the campaign that created the LeadiD token was identified as a call center. |
Responses in this category are limited to a maximum value of 30. | ||
NOTE: Device data points will only be returned for LeadiD tokens generated by a Web campaign script. | ||
device_undefined | 1 | The Device ID was not found. |
device_five_minutes | ## | # leads from this device in the past 5 minutes. |
device_hour | ## | # leads from this device in the past Hour. |
device_twelve_hours | ## | # leads from this device in the past 12 Hours. |
device_day | ## | # leads from this device in the past Day. |
device_week | ## | # leads from this device in the past Week. |
NOTE: IP data points will only be returned for LeadiD tokens generated by a Web campaign script. | ||
ip_five_minutes | ## | # leads from this IP in the past 5 minutes. |
ip_hour | ## | # leads from this IP in the past Hour. |
ip_twelve_hours | ## | # leads from this IP in the past 12 Hours. |
ip_day | ## | # leads from this IP in the past Day. |
ip_week | ## | # leads from this IP in the past Week. |
any 'device_' or 'ip_' Data Point | -1 | The value was blocked by the creator's campaign. |
Lead Velocity | ||
---|---|---|
Data Point | Value | Description |
Responses in this category are limited to a maximum value of 30. | ||
lead_five_minutes | ## | # unique entities prior to this audit, exposed to this LeadiD in the past 5 minutes. |
lead_hour | ## | # unique entities prior to this audit, exposed to this LeadiD in the past hour. |
lead_twelve_hours | ## | # unique entities prior to this audit, exposed to this LeadiD in the past 12 hours. |
lead_day | ## | # unique entities prior to this audit, exposed to this LeadiD in the past day. |
lead_week | ## | # unique entities prior to this audit, exposed to this LeadiD in the past week. |
any 'lead_' Data Point | -1 | The value was blocked by the creator's campaign. |
Consumer Velocity | ||
---|---|---|
Data Point | Value | Description |
Responses in this category are limited to a maximum value of 30. | ||
consumer_five_minutes | ## | # leads from this Consumer in the past 5 minutes. |
consumer_hour | ## | # leads from this Consumer in the past Hour. |
consumer_twelve_hours | ## | # leads from this Consumer in the past 12 Hours. |
consumer_day | ## | # leads from this Consumer in the past Day. |
consumer_week | ## | # leads from this Consumer in the past Week. |
any 'consumer_' Data Point | -1 | The value was blocked by the creator's campaign. |
Lead Lineage | ||
---|---|---|
Data Point | Value | Description |
NOTE: LPC value is required for these data points to be returned | ||
total_entities | ## | Total entities who we know have received this lead (besides you). |
-1 | The value was blocked by the creator's campaign. | |
total_hops | ## | The number of hops a lead took between the generator and you. |
-1 | The value was blocked by the creator's campaign. |
Lead Duplication | ||
---|---|---|
Data Point | Value | Description |
consumer_dupe_check | 00 | Consumer email address has not been seen before |
01 | Consumer email address seen in last 0-7 days | |
02 | Consumer email address seen in last 7-14 days | |
03 | Consumer email address seen in last 14-30 days | |
04 | Consumer email address seen in last 30-60 days | |
05 | Consumer email address seen in last 60-90 days | |
06 | Consumer email address seen in last 3-4 months | |
lead_dupe_check | 00 | LeadiD has not been audited before |
01 | LeadiD has been audited in last 0-7 days | |
02 | LeadiD has been audited in last 7-14 days | |
03 | LeadiD has been audited in last 14-30 days | |
04 | LeadiD has been audited in last 30-60 days | |
05 | LeadiD has been audited in last 60-90 days | |
06 | LeadiD has been audited in last 3-4 months | |
07 | LeadiD has been audited in last 4-5 months | |
08 | LeadiD has been audited in last 5-6 months | |
09 | LeadiD has been audited in last 6-9 months | |
10 | LeadiD has been audited over 9 months ago | |
lead_dupe | 0 | LeadiD has not been previously audited by the same party. |
1 | LeadiD has previously been audited by the same party. | |
lead_dupe_time | # | The timestamp when the LeadiD was previously received. |
lead_dupe_provider | {entity code} | Returns the entity code of the provider who had previously provided the LeadiD being audited. |
Rules Check
Rules Check - Value Definitions | |
---|---|
NOTE: The value variables in this section can return any of the 3 values below | |
Value | Description |
1 | The returned result of the Audit Rule is green. |
2 | The returned result of the Audit Rule is yellow. |
3 | The returned result of the Audit Rule is red. |
Overall Result | ||
---|---|---|
Data Point | Value | Description |
result | # | Overall 'rule' value from the query response, as per flag settings in the Jornaya portal. |
LeadiD Authenticity | ||
---|---|---|
Data Point | Value | Description |
reg_rule | # | Returned flags for the authenticity rule check. |
Lead Age | ||
---|---|---|
Data Point | Value | Description |
age_rule | # | Returned flags for the authenticity rule check. |
Lead Duration | ||
---|---|---|
Data Point | Value | Description |
duration_rule | # | Returned flags for the Lead Duration rule check. |
Data Integrity | ||
---|---|---|
Data Point | Value | Description |
data_integrity_rule | # | Returned flags for the Data Integrity rule check. |
Lead Origin | ||
---|---|---|
Data Point | Value | Description |
url_rule | # | Returned flags for the URL Flag rule check. |
entity_rule | # | Returned flags for the Entity Flag rule check. |
content_not_available_rule | # | Returned flags for the Content Not Available rule check. |
Consumer Origin | ||
---|---|---|
Data Point | Value | Description |
call_center_rule | # | Returned flags for the Call Center rule check. |
device_undefined_rule | # | Yellow or Red flag: device ID could not be found. |
device_five_minutes_rule | # | Yellow or Red flag: consumer device created too many leads in the past 5 Minutes. |
device_hour_rule | # | Yellow or Red flag: consumer device created too many leads in the past hour. |
device_twelve_hours_rule | # | Yellow or Red flag: consumer device created too many leads in the past 12 Hours. |
device_day_rule | # | Yellow or Red flag: consumer device created too many leads in the past Day. |
device_week_rule | # | Yellow or Red flag: consumer device created too many leads in the past Week. |
ip_five_minutes_rule | # | Yellow or Red flag: consumer IP created too many leads in the past 5 Minutes. |
ip_hour_rule | # | Yellow orRed flag: consumer IP created too many leads in the past hour. |
ip_twelve_hours_rule | # | Yellow or Red flag: consumer IP created too many leads in the past 12 Hours. |
ip_day_rule | # | Yellow or Red flag: consumer IP created too many leads in the past Day. |
ip_week_rule | # | Yellow or Red flag: consumer IP created too many leads in the past Week. |
Lead Velocity | ||
---|---|---|
Data Point | Value | Description |
lead_five_minutes_rule | # | Yellow or Red flag: sold too many times in the past 5 minutes. |
lead_hour_rule | # | Yellow or Red flag: sold too many times in the past Hour. |
lead_twelve_hours_rule | # | Yellow or Red flag: sold too many times in the past 12 Hours. |
lead_day_rule | # | Yellow or Red flag: sold too many times in the past Day. |
lead_week_rule | # | Yellow or Red flag: sold too many times in the past Week. |
Consumer Velocity | ||
---|---|---|
Data Point | Value | Description |
consumer_five_minutes_rule | # | Yellow or Red flag: consumer created too many leads in the past 5 Minutes. |
consumer_hour_rule | # | Yellow or Red flag: consumer created too many leads in the past Hour. |
consumer_twelve_hours_rule | # | Yellow or Red flag: consumer created too many leads in the past 12 Hours. |
consumer_day_rule | # | Yellow or Red flag: consumer created too many leads in the past Day. |
consumer_week_rule | # | Yellow or Red flag: consumer created too many leads in the past Week. |
Lead Lineage | ||
---|---|---|
Data Point | Value | Description |
total_entities_rule | # | Yellow or Red flag: lead has been seen by too many entities. |
total_hops_rule | # | Yellow or Red flag: lead took too many hops between the generator and you. |
Lead Duplication | ||
---|---|---|
Data Point | Value | Description |
consumer_dupe_check_rule | # | Flag return for rules set on duplicate LeadiD. |
lead_dupe_check_rule | # | Flag return for rules set on duplicate LeadiD. |
lead_dupe_rule | # | Flag return for rules set on duplicate LeadiD. |
Category Blocking
The following data points will only be returned if the category has been blocked by the creator's campaign. This is different than when the creator blocks individual data point values. Individual data points blocked will return a -1 for the data point. Categories blocked will return a 1 for the category_blocked data point. When a Category is blocked, no individual data points in that Category will be returned. Category blocking supersedes any individual data point blocking.
Lead Data Integrity | ||
---|---|---|
Data Point | Value | Description |
data_integrity_blocked | 1 | The category was blocked by the creator. |
total_hops_rule | # | Returned flag for blocking this category. |
Lead Origin | ||
---|---|---|
Data Point | Value | Description |
url_blocked | 1 | The category was blocked by the creator. |
url_blocked_rule | # | Returned flag for blocking this category. |
entity_blocked | 1 | The category was blocked by the creator. |
entity_blocked_rule | # | Returned flag for blocking this category. |
content_blocked | 1 | The category was blocked by the creator. |
content_blocked_rule | # | Returned flag for blocking this category. |
Consumer Origin | ||
---|---|---|
Data Point | Value | Description |
device_blocked | 1 | The category was blocked by the creator. |
device_blocked_rule | # | Returned flag for blocking this category. |
Lead Velocity | ||
---|---|---|
Data Point | Value | Description |
lead_velocity_blocked | 1 | The category was blocked by the creator. |
lead_velocity_blocked_rule | # | Returned flag for blocking this category. |
Consumer Velocity | ||
---|---|---|
Data Point | Value | Description |
consumer_velocity_blocked | 1 | The category was blocked by the creator. |
consumer_velocity_blocked_rule | # | Returned flag for blocking this category. |
Lead Lineage | ||
---|---|---|
Data Point | Value | Description |
total_entities_blocked | 1 | The category was blocked by the creator. |
total_entities_blocked_rule | # | Returned flag for blocking this category. |
total_hops_blocked | 1 | The category was blocked by the creator. |
total_hops_blocked_rule | # | Returned flag for blocking this category. |
Lead Duplication | ||
---|---|---|
Data Point | Value | Description |
lead_dupe_blocked | 1 | The category was blocked by the creator. |
lead_dupe_blocked_rule | # | Returned flag for blocking this category. |
consumer_dupe_blocked | 1 | The category was blocked by the creator. |
consumer_dupe_blocked_rule | # | Returned flag for blocking this category. |
Field Data Labels
The field data label is used to identify the information being sent in the "data" parameter which allows it to be ingested properly.
Example: f_name; Joe
Label | Description |
Data field values are restricted to 250 characters max per value. | |
f_name | First Name |
l_name | Last Name |
phone1 | Phone1 |
phone2 | Phone2 |
address1 | Address1 |
address2 | Address2 |
city | City |
state | State |
zip | Zip |
Response Data Types and Lengths
Data Point | Type | Max Length |
---|---|---|
age | Int | 2 |
age_rule | Int | 1 |
authentic | Int | 1 |
reg_rule | Int | 1 |
call_center | Int | 1 |
call_center_rule | Int | 1 |
consumer_day | Int | 2 |
consumer_day_rule | Int | 1 |
consumer_dupe_blocked | Int | 1 |
consumer_dupe_blocked_rule | Int | 1 |
consumer_dupe_check | Int | 2 |
consumer_dupe_check_rule | Int | 1 |
consumer_five_minutes | Int | 2 |
consumer_five_minutes_rule | Int | 1 |
consumer_hour | Int | 2 |
consumer_hour_rule | Int | 1 |
consumer_twelve_hours | Int | 2 |
consumer_twelve_hours_rule | Int | 1 |
consumer_velocity_blocked | Int | 1 |
consumer_velocity_blocked_rule | Int | 1 |
consumer_week | Int | 2 |
consumer_week_rule | Int | 1 |
data_integrity | Int | 1 |
data_integrity_blocked | Int | 1 |
data_integrity_blocked_rule | Int | 1 |
data_integrity_default | Array list of data submitted that was the default values. | |
data_integrity_failed | Array list of data submitted that failed data integrity. | |
data_integrity_passed | Array list of data submitted that passed data integrity. | |
data_integrity_rule | Int | 1 |
device_blocked | Int | 1 |
device_blocked_rule | Int | 1 |
device_day | Int | 2 |
device_day_rule | Int | 1 |
device_five_minutes | Int | 2 |
device_five_minutes_rule | Int | 1 |
device_hour | Int | 2 |
device_hour_rule | Int | 1 |
device_twelve_hours | Int | 2 |
device_twelve_hours_rule | Int | 1 |
device_undefined | Int | 1 |
device_undefined_rule | Int | 1 |
device_week | Int | 2 |
device_week_rule | Int | 1 |
duration | Int | 1 |
duration_rule | Int | 1 |
entity_blocked | Int | 1 |
entity_blocked_rule | Int | 1 |
entity_rule | Int | 1 |
entity_value | Int | 1 |
field_disclosures | Array list of field disclosures associated with the field label key passed. These are specific disclosures the Generator has included per field. | |
fields | Array list of elements where the key is the field name and the value is the data_integrity value/outcome. NOTE: email integrity is checked in 3 parts. The complete email is checked. In the event that there is not a match on the complete email address, the data_integrity results for each of these components is also returned in the response. | |
ip_blocked | Int | 1 |
ip_blocked_rule | Int | 1 |
ip_day | Int | 2 |
ip_day_rule | Int | 1 |
ip_five_minutes | Int | 2 |
ip_five_minutes_rule | Int | 1 |
ip_hour | Int | 2 |
ip_hour_rule | Int | 1 |
ip_twelve_hours | Int | 2 |
ip_twelve_hours_rule | Int | 1 |
ip_week | Int | 2 |
ip_week_rule | Int | 1 |
lead_age | Float | 32 bit |
lead_day | Int | 2 |
lead_day_rule | Int | 1 |
lead_dupe | Int | 1 |
lead_dupe_blocked | Int | 1 |
lead_dupe_blocked_rule | Int | 1 |
lead_dupe_check | Int | 2 |
lead_dupe_check_rule | Int | 1 |
lead_dupe_provider | String | 36 |
lead_dupe_rule | Int | 1 |
lead_dupe_time | Float | 32 bit |
lead_duration | Float | 32 bit |
lead_five_minutes | Int | 2 |
lead_five_minutes_rule | Int | 1 |
lead_hour | Int | 2 |
lead_hour_rule | Int | 1 |
lead_twelve_hours | Int | 2 |
lead_twelve_hours_rule | Int | 1 |
lead_velocity_blocked | Int | 1 |
lead_velocity_blocked_rule | Int | 1 |
lead_week | Int | 2 |
lead_week_rule | Int | 1 |
result | Int | 1 |
token | String | 36 |
total_entities | Int | 2 |
total_entities_blocked | Int | 1 |
total_entities_blocked_rule | Int | 1 |
total_entities_rule | Int | 1 |
total_hops | Int | 2 |
total_hops_blocked | Int | 1 |
total_hops_blocked_rule | Int | 1 |
total_hops_rule | Int | 1 |
url_blocked | Int | 1 |
url_blocked_rule | Int | 1 |
url_rule | Int | 1 |
url_value | Int | 1 |
Error Codes
Value | Description |
100 | Internal Error Retry Jornaya side error. Initiate retry logic. |
1000 | Leadid not set The LeadiD value has not been provided or the HTTPS method (GET or POST) is not in the correct format for the LeadiD value to be set. |
1001 | Malformed LeadiD The LeadiD value is either malformed or blank. |
2000 | Account code not set The Account code value has not been provided. |
2001 | Malformed account code The Account code value is either malformed or blank. |
4001 | Malformed Audit Key The audit key is malformed or blank. |
5000 | Invalid Entry Code The entity code provided is not valid. |
6000 | Invalid Account Code and/or Audit Key Either the account code or audit key provided is invalid. |
7000 | Testing not enabled for account The account is not set up for testing. Please contact support@jornaya.com to have this enabled. |
Response Data Types and Lengths
Data Point | Type | Max Length |
disclosure | Int | 1 |
disclosure_rule | Int | 1 |
consent | Int | 1 |
consent_rule | Int | 1 |
type | Int | 1 |
type_rule | Int | 1 |
prominence | Int | 1 |
prominence_value | Float | 32 bit |
prominence_rule | Int | 1 |
contrast | Int | 1 |
contrast_value | Float | 32 bit |
contrast_rule | Int | 1 |
visibility | Int | 1 |
visibility_value | Float | 32 bit |
visibility_rule | Int | 1 |
capture | Int | 1 |
capture_rule | Int | 1 |
stored | Int | 1 |
stored_rule | Int | 1 |
result | Int | 1 |