The Multiple Application Warning (MAW) API surfaces early indicators of a subject's recent lending activity by detecting whether financial institutions have contacted their mobile number via calls or SMS. Each record returned represents a contact event — a phone call, pre-recorded voice message, or text message — made by a lending platform to that number, along with the date it occurred, the contact source, and a risk level classification.

Rather than returning aggregate statistics, MAW returns a timeline of institutional contact events. The pattern of these events — their recency, frequency, source types, and levels — reveals where the subject sits in the lending lifecycle: from a newly approved borrower receiving disbursement confirmations, to a delinquent borrower receiving debt collection calls.

MAW checks are synchronous: results are returned immediately in the API response.

Multiple Application Warning is currently in Beta. A legacy Alpha version is also available — see MAW (Alpha).

Supported Markets

Template ID	Supported Markets
`tpl-maw002001`	India (IN), Mexico (MX), Philippines (PH), Indonesia (ID), Colombia (CO), Thailand (TH)

📘
Mobile Number Privacy
MD5-encrypted mobile number input is accepted. Submit the encrypted value as MD5(countryCode + mobileNumber) — for example, MD5(639559991234) for a Philippine number. This allows you to pass the identifier without transmitting the raw phone number in plaintext.

Understanding the Results

The maw2Items array returned in a successful MAW2 response contains individual contact event records. Each record tells you:

When an institution contacted this number (date)
How they contacted it (source: manual agent call, pre-recorded voice call, or SMS)
Who contacted it (platformId: the unique ID of the lending platform)
Why they contacted it — inferred from the risk level (level)

Reading the events together gives you a picture of the subject's current relationship with lending institutions. A number that appears frequently in recent Level 4 or Level 5 events is likely under active debt collection. A number with many Level 2 entries and recent Level 1 activity suggests a borrower with a healthy repayment record.

Contact Levels

Each event is assigned a level indicating the nature of the contact and the borrower's standing with that institution at the time.

Level	Classification	Description
`1`	White list	Contact related to on-time repayment — the subject repaid on or before the due date
`2`	Secondary white list	Contact related to active lending — the subject is a current borrower in good standing
`3`	Normal list	Informational contact — OTP verification, registration confirmations, or loan application notifications
`4`	Gray list	Early overdue contact — the subject has an outstanding loan overdue by 7 days or fewer
`5`	Black list	Late overdue contact — the subject has an outstanding loan overdue by more than 7 days

Contact Sources

Source	Description
`seat`	Manual agent call. The `duration` field will contain the call length.
`voice`	Pre-recorded or automated voice call
`sms`	Text message

How a MAW2 Request Works

Submit a MAW2 request using POST /beta/maws/requestMaw2. Provide templateId, mobileNumber, countryCode, and consent.
Receive the result synchronously. The API returns the full MAW2 object in the response body. The maw2Items array contains all contact event records found for the subject's mobile number.
Evaluate the events. Review the dates, levels, and sources of the returned events to assess the subject's recent lending activity and repayment standing. An empty maw2Items array with resultCode: SUCCESS means the number was found but has no contact records — not that it returned no data.

The MAW2 Objects

Request Object

Attribute	Type	Required	Description
templateId	string	Yes	The MAW template to use. Use `tpl-maw002001` for the default multi-market template.
consent	object	Yes	Evidence of the subject's consent. See Consent Templates for details.
mobileNumber	string	Yes	The subject's mobile number including country code, no leading zeros. Example: `639559991234`. MD5-encrypted input is also accepted (see note above).
countryCode	string	Yes	ISO 3166 alpha-2 country code for the subject's market. Example: `PH`.

MAW2 Object

This is the object returned in the response.

Attribute	Type	Description
id	string	Unique ID of this MAW2 record. IDs use the prefix `maw-`.
createdAt	date-time	Date and time when this record was created
status	string	Current processing status of the request. See MAW2 Statuses below.
resultCode	string	Final result code of the check. See Result Codes below.
resultMessage	string	Human-readable description of the result
type	string	Always `MAW2` for requests made through this API
requestMeta	object	Echo of the original request parameters sent with the check
maw2Items	array	The contact event records returned for this request. See Item Object below. May be empty if no records were found.
maw3Items	array	Always empty (`[]`) for MAW2 requests. Used by the Borrower Behavior (MAW3) product.

Item Object

Each entry in the maw2Items array represents a single institutional contact event.

Attribute	Type	Description
date	date	The date of the contact event, in `YYYY-MM-DD` format
level	string	Risk level classification of this contact event. See Contact Levels above.
source	string	The contact method. One of: `seat`, `voice`, `sms`. See Contact Sources above.
platformId	string	Unique identifier of the lending platform that made the contact
duration	string	Duration of the call, in seconds. Only present when `source` is `seat`. Null otherwise.
platformTags	array of strings	Category tags for the platform. Possible values include `finance`, `other`.

MAW2 Statuses

Status	Description
`PROCESSING`	The check is currently in progress
`COMPLETED`	The check has completed and results are available
`ERROR`	The check encountered an error and could not be completed

Result Codes

Result Code	Description	Billable
`SUCCESS`	The check completed. Inspect `maw2Items` for contact records — the array may be empty if none were found.	Yes
`NO_DATA`	Smile was unable to return any result for the provided mobile number.	No
`SYSTEM_ERROR`	An internal error occurred. Contact Smile support if this persists.	No
`SERVICE_UNAVAILABLE`	A required data source is temporarily unavailable.	No

📘
Billing Note
MAW2 checks are billed only on SUCCESS. NO_DATA results are not charged. Only the POST /beta/maws/requestMaw2 endpoint is counted for billing — List and Get requests are not charged.

Sample MAW2 data

{
  "id": "maw-e35d521ef8f147c4aa01b7c1af85aaf7",
  "createdAt": "2021-04-14T09:30:24Z",
  "status": "COMPLETED",
  "resultCode": "SUCCESS",
  "resultMessage": "Success!",
  "type": "MAW2",
  "requestMeta": {
    "templateId": "tpl-maw002001",
    "mobileNumber": "639559991234",
    "countryCode": "PH",
    "consent": {
      "type": "Terms And Conditions",
      "version": "1.0.0",
      "consentedWith": "I agree to the terms and conditions.",
      "consentedAt": "2021-04-14T09:30:24Z",
      "consentTemplateId": null
    }
  },
  "maw2Items": [
    {
      "date": "2021-04-14",
      "level": "2",
      "source": "seat",
      "duration": "120",
      "platformId": "5b79399a68524234bb0ead472648282d",
      "platformTags": ["finance"]
    },
    {
      "date": "2021-03-14",
      "level": "3",
      "source": "sms",
      "duration": null,
      "platformId": "5b79399a68524234bb0ead472648282d",
      "platformTags": ["finance"]
    },
    {
      "date": "2021-02-01",
      "level": "4",
      "source": "voice",
      "duration": null,
      "platformId": "7c88411b79635345cc1fbe583759393e",
      "platformTags": ["finance"]
    }
  ],
  "maw3Items": []
}

Sandbox Testing

Use the following values to trigger a successful response in the Sandbox environment. Any other valid mobile number and country code combination will return resultCode: NO_DATA with an empty maw2Items array.

Parameter	Value	Expected Response
`templateId`	`tpl-maw002001`
`countryCode`	`PH`
`mobileNumber`	`639559991234`	`resultCode: SUCCESS`

Endpoints

📘
Shared List and Get Endpoints
The List and Get endpoints are shared with the Borrower Behavior (MAW3) product. When listing, use the mawType=MAW2 query parameter to filter for MAW2 records only.

Endpoint
Create MAW2 check	`POST /beta/maws/requestMaw2`
List MAW checks	`GET /beta/maws`
Retrieve one MAW check	`GET /beta/maws/{id}`