Mobile Intelligence Check

Run a mobile intelligence check

To run a Mobile Intelligence Check, you must create a check with type set to mobile_intelligence_check.

This check requires the client to have a mobile attribute set.

Learn more about Mobile Intelligence Checks.

Get in touch with your Account Manager or contact us to enable this service.

Check request

Attribute	Type	Description
clientId	string	The ID of the client associated with this check. (Required)
type	string	This must be set to mobile_intelligence_check. (Required)

Example request

cURL

curl -X POST https://api.complycube.com/v1/checks \
     -H 'Authorization: <YOUR_API_KEY>' \
     -H 'Content-Type: application/json' \
     -d '{
          "clientId":"CLIENT_ID",
          "type": "mobile_intelligence_check"
        }'

Node.js

const check = await complycube.check.create("CLIENT_ID", {
        type: "mobile_intelligence_check"
});

Python

check = cc_api.check.create(
    'CLIENT_ID',
    'mobile_intelligence_check'
)

PHP

$result = $ccapi->checks()->create(
    'CLIENT_ID',
    [
        'type' => 'mobile_intelligence_check'
    ]
);

.NET

var checkRequest = new CheckRequest {
  clientId = "CLIENT_ID",
  type = "mobile_intelligence_check"
};

var check = await checkApi.CreateAsync(checkRequest);

Result object

The result object is only returned when the status of the check is complete . It has two components - outcome and breakdown.

Outcome

The outcome attribute represents the overall check result. Returned values include:

1. clear: Indicates every analysis type conducted returned a successful result.

2. attention: Indicates at least one of the analysis results requires attention.

Breakdown

The breakdown comprises the following objects:

riskAnalysis object

The risk analysis results. For each conducted analysis, the returned values include:

1. clear: Indicates the analysis returned a successful result.

2. attention: Indicates the analysis returned a result that requires a review.

It has the following constituents:

• validFormat: Indicates if the mobile number is properly formatted and considered valid based on assigned phone numbers available to carriers in that country.

• recentAbuseAnalysis: Indicates if this mobile number has been associated with recent or ongoing fraud.

• isActive: Whether the number is currently active according to the telecom provider.

• digitalNumberAnalysis: Indicates if the number is digital number or a Voice Over Internet Protocol (VOIP).

• riskLevel: A value between 0 and 100 that estimates how likely a mobile number is associated with fraudulent activity. You may use the ranges below as guidance when interpreting results:

  • 0–50: No indicators of fraud detected.

  • 51–75: Suspicious range. Not necessarily fraudulent, but higher scores here suggest a stronger likelihood of risky or harmful activity.

  • 76–100: High-risk number. Strongly associated with fraud or abuse and should not be trusted.

phoneData object

Data extracted about the mobile number and its carrier. It has the following constituents:

• carrier: The name of the carrier the mobile number is registered to.

Sample Response

{
    "id": "6231d54079f59b1530fc76e3",
    "entityName": "John Doe",
    "type": "mobile_intelligence_check",
    "clientId": "6230d4ab58ed4a434afbf2cc",
    "status": "complete",
    "result": {
        "outcome": "clear",
        "breakdown": {
            "riskAnalysis": {
                "validFormat": "clear",
                "recentAbuseAnalysis": "clear",
                "isActive": "clear",
                "digitalNumberAnalysis": "clear",
                "riskLevelAnalysis": "clear",
                "breakdown": {
                    "riskLevelScore": 12
                }
            },
            "phoneData": {
                "carrier": "Vodafone"
            }
        }
    },
    "updatedAt": "2025-01-01T12:17:06.046Z",
    "createdAt": "2025-01-01T12:17:04.809Z"
}