Multi Platform Detection

Note : Please first check the Glossary for basic information about ADVANCE API.

Code Sample

curl -X POST \
-H "X-ACCESS-TOKEN: {Your Access Token}" \
-H "Content-Type: application/json" \
-d '{
    "includeSelf":"include",
    "phoneNumber":"+6281116725888",
    "idNumber":"7271045005860004"
}' \

"https://api.advance.ai/openapi/default-detection/v11/multi-platform"

Request Url

https://api.advance.ai/openapi/default-detection/v11/multi-platform
POST (application/json)

Notes:

ADVANCE service is deployed overseas. If your test/official environment is in China, please request the service via VPN to avoid packet loss, service timeout and other problems

Request Header Parameters:

Parameter	Description
X-ACCESS-TOKEN	`string` Please Click here to get your access token

Request Parameters:

Parameter	Description
idNumber	`string` customer’s ID number (NIK), must be a 16 digit number
phoneNumber	`string` The customer’s phone number must be start with “+628” and follow 8-12 digits number e.g. +6281241472136
includeSelf	`string` `optional` The values should be `include`(include this account query) or `exclude`(exclude this account query), defaults to exclude

Example of SUCCESS Response:

{
    "code":"SUCCESS",
    "message":"OK",
    "data":{
        "GD_X_1":3825.490574,
        "GD_X_2":81.782039,
        "GD_X_3":null,
        "GD_X_4":null,
        "GD_X_5":null,
        "GD_X_6":null,
        "GD_X_7":null,
        "GD_X_8":null,
        "GD_X_9":null,
        "GD_X_10":null,
        "GD_X_11":null,
        "GD_X_12":null,
        "GD_X_13":null,
        "GD_X_14":null,
        "GD_X_15":null,
        "GD_X_16":null,
        "GD_X_17":null,
        "GD_X_18":null,
        "GD_X_19":null,
        "GD_X_20":null,
        "GD_X_21":null,
        "GD_X_22":1.0,
        "GD_X_23":1.0,
        "GD_X_24":1.0,
        "GD_X_25":1.0,
        "GD_X_26":1.0,
        "GD_X_27":0.2,
        "GD_X_28":0.2,
        "GD_X_29":0.2,
        "GD_X_30":0.2,
        "GD_X_31":2808.488889,
        "GD_X_32":2808.488889,
        "GD_X_33":null,
        "GD_X_34":null,
        "GD_X_35":null,
        "GD_X_36":null,
        "GD_X_37":null,
        "GD_X_38":null,
        "GD_X_39":null,
        "GD_X_40":null,
        "GD_X_41":null,
        "GD_X_42":null,
        "GD_X_43":null,
        "GD_X_44":null,
        "GD_X_45":null,
        "GD_X_46":null,
        "GD_X_47":null,
        "GD_X_48":null,
        "GD_X_49":null,
        "GD_X_50":null,
        "GD_X_51":null,
        "GD_X_52":null,
        "GD_X_53":null,
        "GD_X_54":null,
        "GD_X_55":1.0,
        "GD_X_56":1.0,
        "GD_X_57":0.1,
        "GD_X_58":0.1,
        "GD_X_59":0.2,
        "GD_X_60":0.2
    },
    "extra":null,
    "transactionId":"489e790c921d2805",
    "pricingStrategy":"PAY"
}

Example NO_QUERY_RECORD Response:

{
    "code":"NO_QUERY_RECORD",
    "message":"No query record",
    "data":{
        "GD_X_1":null,
        "GD_X_2":null,
        "GD_X_3":null,
        "GD_X_4":null,
        "GD_X_5":null,
        "GD_X_6":null,
        "GD_X_7":null,
        "GD_X_8":null,
        "GD_X_9":null,
        "GD_X_10":null,
        "GD_X_11":null,
        "GD_X_12":null,
        "GD_X_13":null,
        "GD_X_14":null,
        "GD_X_15":null,
        "GD_X_16":null,
        "GD_X_17":null,
        "GD_X_18":null,
        "GD_X_19":null,
        "GD_X_20":null,
        "GD_X_21":null,
        "GD_X_22":null,
        "GD_X_23":null,
        "GD_X_24":null,
        "GD_X_25":null,
        "GD_X_26":null,
        "GD_X_27":null,
        "GD_X_28":null,
        "GD_X_29":null,
        "GD_X_30":null,
        "GD_X_31":null,
        "GD_X_32":null,
        "GD_X_33":null,
        "GD_X_34":null,
        "GD_X_35":null,
        "GD_X_36":null,
        "GD_X_37":null,
        "GD_X_38":null,
        "GD_X_39":null,
        "GD_X_40":null,
        "GD_X_41":null,
        "GD_X_42":null,
        "GD_X_43":null,
        "GD_X_44":null,
        "GD_X_45":null,
        "GD_X_46":null,
        "GD_X_47":null,
        "GD_X_48":null,
        "GD_X_49":null,
        "GD_X_50":null,
        "GD_X_51":null,
        "GD_X_52":null,
        "GD_X_53":null,
        "GD_X_54":null,
        "GD_X_55":null,
        "GD_X_56":null,
        "GD_X_57":null,
        "GD_X_58":null,
        "GD_X_59":null,
        "GD_X_60":null
    },
    "extra":null,
    "transactionId":"e5069dac31e066ae",
    "pricingStrategy":"PAY"
}

Example of PARAMETER_ERROR Response:

{
    "code":"PARAMETER_ERROR",
    "message":"Invalid phone number, please check your phone number format or call segment",
    "data":null,
    "extra":null,
    "transactionId":"5c6b6b6d19596572",
    "pricingStrategy":"FREE"
}

{
    "code":"PARAMETER_ERROR",
    "message":"Invalid ID number, please check the id format",
    "data":null,
    "extra":null,
    "transactionId":"e8274659743521d6",
    "pricingStrategy":"FREE"
}

{
    "code":"PARAMETER_ERROR",
    "message":"Parameter should not be empty",
    "data":null,
    "extra":null,
    "transactionId":"1570b10046406907",
    "pricingStrategy":"FREE"
}

{
    "code":"PARAMETER_ERROR",
    "message":"IncludeSelf value should be include or exclude",
    "data":null,
    "extra":null,
    "transactionId":"bc8dc632ebad75ef",
    "pricingStrategy":"FREE"
}

Example of RETRY_LATER Response:

{
    "code":"RETRY_LATER",
    "message":"Query failed, please retry after the suggested time in HTTP Header.",
    "data":null,
    "extra":null,
    "transactionId":"911b991423cd7e1e",
    "pricingStrategy":"FREE"
}

Response Description

Parameter	Description
code	Response status code
message	Status Code Explanation
transactionId	the request id, the max length is 64
data	Please check the Features value details
pricingStrategy	whether the request will be charged, enum type: `FREE`, `PAY`
extra	Extra response info (Exception Message)

Features value details

Field Name	Description
GD_X_1	`float` time difference in hour between the apply time and the FIRST time point this applicant’s ID number used our service within 8640 hours(360 days)
GD_X_2	`float` time difference in hour between the apply time and the LAST time point this applicant’s ID number used our service within 8640 hours(360 days)
GD_X_3	`float` number of customers from P2P segmentation within the last 24 hours (1 day) checking applicant’s ID number
GD_X_4	`float` number of customers from P2P segmentation within the last 168 hours (7 days) checking applicant’s ID number
GD_X_5	`float` number of customers from P2P segmentation within the last 720 hours (30 days) checking applicant’s ID number
GD_X_6	`float` number of customers from P2P segmentation within the last 2160 hours (90 days) checking applicant’s ID number
GD_X_7	`float` number of customers from P2P segmentation within the last 4320 hours (180 days) checking applicant’s ID number
GD_X_8	`float` number of customers from P2P segmentation within the last 8640 hours (360 days) checking applicant’s ID number
GD_X_9	`float` number of customers from MULTI_FINANCE segmentation within the last 24 hours (1 day) checking applicant’s ID number
GD_X_10	`float` number of customers from MULTI_FINANCE segmentation within the last 168 hours (7 days) checking applicant’s ID number
GD_X_11	`float` number of customers from MULTI_FINANCE segmentation within the last 720 hours (30 days) checking applicant’s ID number
GD_X_12	`float` number of customers from MULTI_FINANCE segmentation within the last 2160 hours (90 days) checking applicant’s ID number
GD_X_13	`float` number of customers from MULTI_FINANCE segmentation within the last 4320 hours (180 days) checking applicant’s ID number
GD_X_14	`float` number of customers from MULTI_FINANCE segmentation within the last 8640 hours (360 days) checking applicant’s ID number
GD_X_15	`float` number of customers from LOAN_SUPERMARKET segmentation within the last 24 hours (1 day) checking applicant’s ID number
GD_X_16	`float` number of customers from LOAN_SUPERMARKET segmentation within the last 168 hours (7 days) checking applicant’s ID number
GD_X_17	`float` number of customers from LOAN_SUPERMARKET segmentation within the last 720 hours (30 days) checking applicant’s ID number
GD_X_18	`float` number of customers from LOAN_SUPERMARKET segmentation within the last 2160 hours (90 days) checking applicant’s ID number
GD_X_19	`float` number of customers from LOAN_SUPERMARKET segmentation within the last 4320 hours (180 days) checking applicant’s ID number
GD_X_20	`float` number of customers from LOAN_SUPERMARKET segmentation within the last 8640 hours (360 days) checking applicant’s ID number
GD_X_21	`float` number of customers from OTHER segmentation within the last 24 hours (1 day) checking applicant’s ID number
GD_X_22	`float` number of customers from OTHER segmentation within the last 168 hours (7 days) checking applicant’s ID number
GD_X_23	`float` number of customers from OTHER segmentation within the last 720 hours (30 days) checking applicant’s ID number
GD_X_24	`float` number of customers from OTHER segmentation within the last 2160 hours (90 days) checking applicant’s ID number
GD_X_25	`float` number of customers from OTHER segmentation within the last 4320 hours (180 days) checking applicant’s ID number
GD_X_26	`float` number of customers from OTHER segmentation within the last 8640 hours (360 days) checking applicant’s ID number
GD_X_27	`float` percentile of number of customers within the last 720 hours (30 days) checking applicant’s ID number
GD_X_28	`float` percentile of number of customers within the last 2160 hours (90 days) checking applicant’s ID number
GD_X_29	`float` percentile of number of customers within the last 4320 hours (180 days) checking applicant’s ID number
GD_X_30	`float` percentile of number of customers within the last 8640 hours (360 days) checking applicant’s ID number
GD_X_31	`float` time difference in hour between the apply time and the FIRST time point this applicant’s phone number used our service within 8640 hours(360 days)
GD_X_32	`float` time difference in hour between the apply time and the LAST time point this applicant’s phone number used our service within 8640 hours(360 days)
GD_X_33	`float` number of customers from P2P segmentation within the last 24 hours (1 day) checking applicant’s phone number
GD_X_34	`float` number of customers from P2P segmentation within the last 168 hours (7 days) checking applicant’s phone number
GD_X_35	`float` number of customers from P2P segmentation within the last 720 hours (30 days) checking applicant’s phone number
GD_X_36	`float` number of customers from P2P segmentation within the last 2160 hours (90 days) checking applicant’s phone number
GD_X_37	`float` number of customers from P2P segmentation within the last 4320 hours (180 days) checking applicant’s phone number
GD_X_38	`float` number of customers from P2P segmentation within the last 8640 hours (360 days) checking applicant’s phone number
GD_X_39	`float` number of customers from MULTI_FINANCE segmentation within the last 24 hours (1 day) checking applicant’s phone number
GD_X_40	`float` number of customers from MULTI_FINANCE segmentation within the last 168 hours (7 days) checking applicant’s phone number
GD_X_41	`float` number of customers from MULTI_FINANCE segmentation within the last 720 hours (30 days) checking applicant’s phone number
GD_X_42	`float` number of customers from MULTI_FINANCE segmentation within the last 2160 hours (90 days) checking applicant’s phone number
GD_X_43	`float` number of customers from MULTI_FINANCE segmentation within the last 4320 hours (180 days) checking applicant’s phone number
GD_X_44	`float` number of customers from MULTI_FINANCE segmentation within the last 8640 hours (360 days) checking applicant’s phone number
GD_X_45	`float` number of customers from LOAN_SUPERMARKET segmentation within the last 24 hours (1 day) checking applicant’s phone number
GD_X_46	`float` number of customers from LOAN_SUPERMARKET segmentation within the last 168 hours (7 days) checking applicant’s phone number
GD_X_47	`float` number of customers from LOAN_SUPERMARKET segmentation within the last 720 hours (30 days) checking applicant’s phone number
GD_X_48	`float` number of customers from LOAN_SUPERMARKET segmentation within the last 2160 hours (90 days) checking applicant’s phone number
GD_X_49	`float` number of customers from LOAN_SUPERMARKET segmentation within the last 4320 hours (180 days) checking applicant’s phone number
GD_X_50	`float` number of customers from LOAN_SUPERMARKET segmentation within the last 8640 hours (360 days) checking applicant’s phone number
GD_X_51	`float` number of customers from OTHER segmentation within the last 24 hours (1 day) checking applicant’s phone number
GD_X_52	`float` number of customers from OTHER segmentation within the last 168 hours (7 days) checking applicant’s phone number
GD_X_53	`float` number of customers from OTHER segmentation within the last 720 hours (30 days) checking applicant’s phone number
GD_X_54	`float` number of customers from OTHER segmentation within the last 2160 hours (90 days) checking applicant’s phone number
GD_X_55	`float` number of customers from OTHER segmentation within the last 4320 hours (180 days) checking applicant’s phone number
GD_X_56	`float` number of customers from OTHER segmentation within the last 8640 hours (360 days) checking applicant’s phone number
GD_X_57	`float` percentile of number of customers within the last 720 hours (30 days) checking applicant’s phone number
GD_X_58	`float` percentile of number of customers within the last 2160 hours (90 days) checking applicant’s phone number
GD_X_59	`float` percentile of number of customers within the last 4320 hours (180 days) checking applicant’s phone number
GD_X_60	`float` percentile of number of customers within the last 8640 hours (360 days) checking applicant’s phone number

Response Code

Status Code	Message
`NO_QUERY_RECORD`	`pay` No query record

Note: Don’t Forget to add handler for these Status Codes in Glossary as well

Token Authentication

Request Parameters:

Parameter	Description
accessKey	`string` the accessKey
timestamp	`string` 13-digit-long timestamp, suggested 300 seconds before or after the current time when requesting the token
signature	`string` Combined accessKey, secretKey and timestamp, encrypted by SHA256. eg. accessKey: sampleaccesskey secretKey: samplesecretkey timestamp: 1665993522952 Combined: sampleaccesskeysamplesecretkey1665993522952 Encrypted based on the combined: 02209bbeaf0d0a3dd587f6a1ba22f84c98d142e3b545e77db7e4906ca56349f5
periodSecond	`string` `optional` Validity period defaults to 3600 seconds, minimum 60 seconds, maximum 86400 seconds. Unit is seconds

Note:

You can find accessKey, secretKey on the Websaas Platform -> Account -> Account Management
The timestamp in the “signature” must be consistent with parameter timestamp
Please remember to re-obtain a new valid token to do the authentication for the open APIs when the previous one is expired

Code Sample

curl -X POST \
-H "Content-Type: application/json" \
-d '{"accessKey":"22********70b","signature":"f786441e7b3d95f*****************853a5a244f9522","timestamp":1648785145789,"periodSecond":120}' \ 
"https://api.advance.ai/openapi/auth/ticket/v1/generate-token"

Request Url

https://api.advance.ai/openapi/auth/ticket/v1/generate-token
POST (application/json)

Example of Success Response:

{
    "code":"SUCCESS",
    "message":"OK",
    "data":{
    "token":"eyJhbGciOiJIUzUxMiJ9.eyJpc3MiOiJoNV9saXZlbmVzcyIsInN1YiI6IntcImN1c3RvbWVySWRcIjo1NTAwMDI4MixcImFjY291bnRJZFwiOjU1MDAwMjg0LFwicmVhbElwXCI6XCI0NS4yNTEuMTA3LjExMVwifSIsImF1ZCI6IldFQiIsImlhdCI6MTY0MjU4MDA3MiwiZXhwIjoxNjQyNTgwMTkyfQ.HmIDcuSW67A59x7bnumjGp0Wdcz-FmoDrnHF1YGui6wVPfulLn4Izonay5LQnySgph1dbyC1E0LtifS-BJo8VA",
    "expiredTime":1642580192430
    },
    "extra":null,
    "transactionId":"6c2c50a3049ce67e",
    "pricingStrategy":"FREE"
}

Example of PARAMETER_ERROR Response:

{
    "code":"PARAMETER_ERROR",
    "message":"Parameter should not be empty",
    "data":null,
    "extra":null,
    "transactionId":"040e769e38f87e3e",
    "pricingStrategy":"FREE"
 }

{
    "code":"PARAMETER_ERROR",
    "message":"Timestamp error",
    "data":null,
    "extra":null,
    "transactionId":"a9c2a6c199ad5db5",
    "pricingStrategy":"FREE"
}

{
    "code":"PARAMETER_ERROR",
    "message":"Signature error",
    "data":null,
    "extra":null,
    "transactionId":"00b05cb9cf6f0fed",
    "pricingStrategy":"FREE"
}

Example of ACCOUNT_DISABLED Response:

{
    "code":"ACCOUNT_DISABLED",
    "message":"Account Disabled",
    "data":null,
    "extra":null,
    "transactionId":"5e00fded1272490e",
    "pricingStrategy":"FREE"
}

Example of CLIENT_ERROR Response:

{
    "code":"CLIENT_ERROR",
    "message":"HTTP 400 - Bad Request",
    "data":null,
    "extra":null,
    "transactionId":"bd5d5653c45d4c6e",
    "pricingStrategy":"FREE"
 }

Response Description:

Parameter	Description
`code`	Response Status Code
`message`	Message returned from server
`data`	`token` AccessToken
	`expiredTime` Expiration timestamp
`extra`	Extra response info such as exception message
`transactionId`	the request id, the max length is 64
`pricingStrategy`	whether the request will be charged, enum type: `FREE`, `PAY`

Response Code

Status Code	Message
`SUCCESS`	`free` OK
`PARAMETER_ERROR`	`free` Parameter should not be empty
	`free` Timestamp error
	`free` Signature error
`ACCOUNT_DISABLED`	`free` Account Disabled
`CLIENT_ERROR`	`free` HTTP 400 - Bad Request

Glossary

Welcome to the Glossary!

Please read the following to understand how ADVANCE API system, for a smooth integration. We will explain all the basics you need to know about our API.

Status Code

Our API responses will contain a Status Code indicating the result of the API call, whether it was successful, or an error occurred during the process
Each API will also have its own unique Status Codes that can only be found in the responses of the API
Your API usage will be charged based on the response Status Code, each Status Code listed in our API document will have either a free or pay tag with it
free means you will not be charged and paymeans that you will be charged
pay means you will be charged if the API response contains the said status code
Below are the commonly used Status Codes, these status codes could appear in all our API responses, so please remember to add a handler for these Status Codes

Notes:

Please use ‘Status Code’ in your strategy instead of ‘Message’, as 'Message’ is a detailed explanation for developer’s reference and may update without ADVANCE Notice.

Status Code	Message
`SUCCESS`	`pay` OK
`ERROR`	`free` Server error
`EMPTY_PARAMETER_ERROR`	`free` Parameter should not be empty
`INSUFFICIENT_BALANCE`	`free` Insufficient balance, please top up or contact your sales manager for help
`SERVICE_BUSY`	`free` Messages may look like: Rate limit is exceeded, please retry after the suggested time in HTTP Header. Retry-After :10s p.s. Please also note that this code may migrate to HTTP 429 Too Many Requests in the future. Quota exceeded: You have exceeded the daily quota for free queries, please contact out tech support for help
`IAM_FAILED`	`free` Access denied. Messages may look like: You are not authorized by the Identity and Access Management system Access Key not found Token not found or expired Access Key not found or expired Account not authorized for this country Account not authorized for this domain Account is expired. Please contact your sales manager for help Account is disabled. Please contact your sales manager for help Access denied: Token not found or expired
`PARAMETER_ERROR`	`free` The message is detailed error description, may includes: Parameter should not be empty Invalid phone number, please check your phone number format etc. p.s. Mobile number format should be country code + phone number(without leading 0 or dash or space e.g. +xx12345678); fixed-line number should be country code + area code + number(without leading 0)
`OVER_QUERY_LIMIT`	`free` Messages may look like: Quota exceeded. you have exceeded free query quota, please contact your sales manager for help Quota exceeded: You have exceeded free query quota for test account, please contact your sales manager for help
`CLIENT_ERROR`	`free` HTTP client error. Messages may look like: HTTP 400 - Bad Request HTTP 404 - Not Found HTTP 405 - Method Not Allowed etc. If you get this error, please check the API document or contact our tech support for help.
`RETRY_LATER`	`free` Query failed, please retry after the suggested time in HTTP Header. Retry-After :10s

Notes:

If the Status Code is SUCCESS, it may not be charged. Please check the code returned by each interface

Request URL & Parameters

Request URL can be found at each API document along with the request method (POST or GET or other request method) and Content Type (application/json or other content type)
Some parameters will have optional tag on them, this means the parameter is not mandatory for the request and they can be empty, however adding them might produce more accurate result, for example : Company check, zip code is an optional parameter but adding zip code parameter will return all the companies around that said zip code instead of all around Indonesia.
If a parameter does not have an optional tag, it means the parameter is mandatory and making request without them will return EMPTY_PARAMETER_ERROR response
Every parameter has a data type such as string, integer and file, please double check the parameter data type before making any request
Here’s an example of parameter explanation that can be found on each API document

Parameter	Description
requestString	`string` String value for API request
requestFile	`file` Request file for API request
requestInteger	`optional` `integer` Number value for API request

Response

ADVANCE API responds in JSON format
ADVANCE API response consists of 4 fields:
- code the Status Code;
- message detailed explanation of the Status Code;
- extra an exception message (should be empty most of the time);
- data the response content from ADVANCE;
Each service has its own data format, outlined in the API document
If the response format is very complicated (multiple different JSON object, nested JSON object), please refer to the Breakdown section of the Response Explanation
transactionId: It is strongly recommended to save the transactionId.
The following is an example of Response Explanation found in each API document:

Parameter	Description
code	API Status Code
message	Status Code Explanation
data	`field1`: explanation of the first information that will be returned from ADVANCE
	`field2`: explanation of the second information that will be returned from ADVANCE
extra	Extra response info (Exception Message)

Image Quality Requirements

The services check and extract the necessary information from the uploaded images, hence please ensure the uploaded images satisfy the following criteria:
- Is in one of the following image formats: PNG / JPG / JPEG
- Below 2 MB file size
- Minimum resolution of 256 x 256
- Maximum resolution of 4096 x 4096
For OCR services please also ensure that the uploaded images satisfy the following criteria:
- ID Card’s ratio in the uploaded photo is not so small that the words in the ID Card are unreadable
- ID Card’s orientation is in Vertical or Horizontal position and NOT heavily tilted (around 45 degree)
- Nothing is covering up the words in the ID Card (ex: Light Spot, Dirt, Ink, Shadow, etc)
- Have a clean background (No words or other picture in the background)