Skip to main content

Scoring Services

add score​

You can use this service to add two scores. For example, You have an Integer named score1 with the value of 10 and another Integer named score2 with the value of 25. The API will return an integer with value of 35.

URL:

https://api.rightwave.net/rdn/api/ss/addScore?int_score1={Marketo token for int_score1}&int_score2={Marketo token for int_score2}

Headers:

Key NameValueDescription
auth-key5wt-be28f07942848582b5915443use for authentication
Content-Typeapplication/jsonaccept application/json

Query Parameters:

Parameter NameData TypeDescription
int_score1Integerfirst input for addscore
int_score2Integersecond input for addscore

Output:

{
"success": true,
"input": {
"int_score1": "3",
"int_score2": "2"
},
"result": {
"sum": 5
},
"requestId": "21666676345885609"
}

Example:

curl -X GET \
-H 'Content-Type: application/json' \
-H 'auth-key: 5wt-be28f07942848582b59154453' \
"https://api.rightwave.net/rdn/api/ss/addScore?int_score1=3&int_score2=2"

junkScore​

You can use the Junk Score service to assess the likelihood of a profile being genuine or potentially problematic based on various profile attributes such as first name, last name, email, company name, and job title.

The Junk Score service applies rules and algorithms based on various parameters:

  • Data Validation: Checks for suspicious or irregular patterns in the provided information.
  • Comparison to Known Patterns: Compares the provided data with known patterns of junk profiles.
  • Algorithmic Scoring: Assigns weighted scores to different profile attributes.

Scores range from 0 to 100:

  • 0 — highly favorable, authentic profile.
  • Above 50 — high likelihood of the profile being junk or problematic.
  • 0–50 — low/medium risk; can be reviewed.

URL:

https://api.rightwave.com/rdn/api/ss/junkScore?inputfirstName={Marketo token for inputfirstName}&inputlastName={Marketo token for inputlastName}&inputemail={Marketo token for inputemail}&inputcompanyName={Marketo token for inputcompanyName}&inputtitle={Marketo token for inputtitle}

Headers:

Key NameValueDescription
auth-key62m-8db697ee26b6eb4e17876775Use for authentication
Content-Typeapplication/jsonHeader for Content-Type

Query Parameters:

Parameter NameData TypeDescription
inputfirstNameStringInput for junkScore
inputlastNameStringInput for junkScore
inputemailStringInput for junkScore
inputcompanyNameStringInput for junkScore
inputtitleStringInput for junkScore

Output:

{
"success": true,
"input": {
"inputfirstName": "first name",
"inputlastName": "last name",
"inputemail": "email address",
"inputcompanyName": "company name",
"inputtitle": "title"
},
"result": {
"output": 10,
"reasons": []
},
"requestId": "21666676345885609"
}

Example:

curl -X GET \
-H 'Content-Type: application/json' \
-H 'auth-key: 62m-8db697ee26b6eb4e17876775' \
"https://api.rightwave.com/rdn/api/ss/junkScore?inputfirstName=Geoff&inputlastName=Schmidt&inputemail=gschmidt@directdigitalholdings.com&inputcompanyName=Direct Digital Holdings&inputtitle=Other"

junkScoreAI​

You can use the Junk Score service with AI to assess the likelihood of a profile being genuine or potentially problematic based on various profile attributes such as first name, last name, email, company name, and job title.

The Junk Score service generates an overall score (junk value) along with AI reasoning. Scores range from 0 to 100:

  • 0 — highly favorable, authentic profile.
  • Above 50 — high likelihood of the profile being junk or problematic.
  • 0–50 — low/medium risk; can be reviewed.

Example Input:

  • First Name: "Geoff", Last Name: "Schmidt", Email: "gschmidt@directdigitalholdings.com", Company: "Direct Digital Holdings", Title: "Partner and Senior Software Engineer"

Example Output:

{
"success": true,
"input": {
"inputFirstName": "Geoff",
"inputLastName": "Schmidt",
"inputEmail": "gschmidt@directdigitalholdings.com",
"inputCompanyName": "Direct Digital Holdings",
"inputTitle": "Other"
},
"result": {
"score": 10,
"reasonAI": "The input record contains a valid email address from a seemingly legitimate domain, a plausible company name that matches the email domain, and a recognizable first and last name. The 'Other' title is not ideal, but it's not entirely non-informative and avoids adding substantial points to the junk score. No placeholder values were detected. Overall, the data appears to be of relatively high quality and suggests a business-related record."
},
"requestId": "13531748353696020892"
}

URL:

https://api.rightwave.com/rdn/api/ss/junkScoreAI?inputFirstName={Marketo token for inputFirstName}&inputLastName={Marketo token for inputLastName}&inputEmail={Marketo token for inputEmail}&inputCompanyName={Marketo token for inputCompanyName}&inputTitle={Marketo token for inputTitle}

Headers:

Key NameValueDescription
auth-key62m-8db697ee26b6eb4e17876775Use for authentication
Content-Typeapplication/jsonHeader for Content-Type

Query Parameters:

Parameter NameData TypeDescription
inputFirstNameStringInput for junkScoreAI
inputLastNameStringInput for junkScoreAI
inputEmailStringInput for junkScoreAI
inputCompanyNameStringInput for junkScoreAI
inputTitleStringInput for junkScoreAI

Example:

curl -X GET \
-H 'Content-Type: application/json' \
-H 'auth-key: 62m-8db697ee26b6eb4e17876775' \
"https://api.rightwave.com/rdn/api/ss/junkScoreAI?inputFirstName=Geoff&inputLastName=Schmidt&inputEmail=gschmidt@directdigitalholdings.com&inputCompanyName=Direct Digital Holdings&inputTitle=Other"