Get My Organization Users
https://api.sanctionscanner.com/api/Operations/GetMyOrganizationUsers
This service allows you to list the users in your organization. The “GET” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | Result Class |
Result Information. The following internal table describes the internal parameters. |
Parameter Name | Data Type | Description |
---|---|---|
UserGuidId | String | Unique Guid Id of user |
NameSurname | String | Name Surname of user |
String | Email Address of user |
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
GET /api/Operations/GetMyOrganizationUsers
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": [
{
"UserGuidId": "*****-*****-*****",
"NameSurname": "*******",
"Email": "*********"
},
{
"UserGuidId": "*****-*****-*****",
"NameSurname": "*******",
"Email": "*********"
}
]
}
Assign a User To a Search
https://api.sanctionscanner.com/api/Operations/AssignUserToSearch
This service is used to assign users to a search.The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
https://appv2.sanctionscanner.com/CaseManagement/Index
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Scan Id Of Search (Example: D0000001) |
UserGuidId | String | Yes | Guid Id Of User To Assign |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call must be made using AssignUserToSearch.
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"scanId":"D0000000000",
"UserGuidId":"*****-*****-*****"
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Assign a User To Batch Search
https://api.sanctionscanner.com/api/Operations/AssignUserToBatch
This service is used to assign users to a batch search as bulk. With this API, all related searches in this batch assigned to the user. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
https://appv2.sanctionscanner.com/CaseManagement/Index
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
BatchId | String | Yes | Batch Id Of Batch Search (Example: BS00001) |
UserGuidId | String | Yes | Guid Id Of User To Assign |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call must be made using AssignUserToBatch.
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"BatchId":"BS0000000000",
"UserGuidId":"*****-*****-*****"
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Remove Assigned User From Search
https://api.sanctionscanner.com/api/Operations/RemoveAssignedUserFromSearch
This service is used to remove assigned user from search. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Scan Id Of Search (Example: D0000001) |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call is updated guid using the RemoveAssignedUserFromSearch.
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"scanId":"D0000000000",
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Set Search's Match Status
https://api.sanctionscanner.com/api/Operations/SetSearchMatchStatus
This service is used to set match status to a search. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
https://appv2.sanctionscanner.com/CaseManagement/Index
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Scan Id Of Search (Example: D00000001) |
StatusId | Integer | No |
Id Of Match Status (Default: 0)
|
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call is updated guid using the SetSearchMatchStatus.
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"scanId":"D0000000000",
"StatusId":"0"
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Set Search's Risk Level
https://api.sanctionscanner.com/api/Operations/SetSearchRiskLevel
This service is used to set risk level to a search. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
https://appv2.sanctionscanner.com/CaseManagement/Index
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Scan Id Of Search (Example: D00000001) |
RiskLevelId | Integer | No |
Id Of Risk Level (Default: 0)
|
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call is updated guid using the SetSearchRiskLevel.
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"scanId":"D0000000000",
"RiskLevelId":"0"
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Add Memo Notes To Search
https://api.sanctionscanner.com/api/Operations/AddMemoToSearch
This service is used to add memo to a search. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
https://appv2.sanctionscanner.com/CaseManagement/Index
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Scan Id Of Search (Example: D0000001) |
Memo | String | Yes | Text Of Memo |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call is updated guid using the AddMemoToSearch.
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"scanId":"D0000000000",
"Memo":"**************** *** ** **"
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Get Memo List By Scan Id
https://api.sanctionscanner.com/api/Operations/GetMemoListByScanId?scanId=ScanId
This service is used to get memos of a search. The “GET” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
https://appv2.sanctionscanner.com/CaseManagement/Index
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Scan Id Of Search (Example: D0000001) |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"scanId":"D0000000000",
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null,
"ScanId": null,
"MemoList": [
{
"MemoId": "*******",
"Memo": "*******",
},
{
"MemoId": "*******",
"Memo": "*******",
}
]
}
Remove Memo By Scan
https://api.sanctionscanner.com/api/Operations/RemoveMemoByScan
This service is used to remove a memo from a search. The “GET” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
https://appv2.sanctionscanner.com/CaseManagement/Index
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
MemoId | String | Yes | Memo Id Of Search (Example: 1234) |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call is updated guid using the RemoveMemoByScan
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request GET /api/Operations/RemoveMemoByScan
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Remove Scan
https://api.sanctionscanner.com/api/Operations/RemoveScan
This service is used to remove a search. The “GET” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
https://appv2.sanctionscanner.com/CaseManagement/Index
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Id Of Scan (Example: "scanId":"D0000000000") |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call is updated guid using the Remove Scan
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request GET /api/Operations/RemoveScan
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Get Close Case Reasons
https://api.sanctionscanner.com/api/Operations/GetMyOrganizationCloseReasons
This service allows you to list the users in your organization. The “GET” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | Result Class |
Result Information. The following internal table describes the internal parameters. |
Parameter Name | Data Type | Description |
---|---|---|
ReasonId | Int | Reason Id of close reason |
Description | String | Description of close reason |
Guid | String | Guid of close reason |
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
GET /api/Operations/GetMyOrganizationCloseReasons
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": [
{
"ReasonId": 1,
"Description": "*******",
"Guid": "*****-*****-*****",
},
{
"ReasonId": 1,
"Description": "*******",
"Guid": "*****-*****-*****",
}
]
}
Close Case By ScanId
https://api.sanctionscanner.com/api/Operations/CloseCaseByScanId
This service is used to close case. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Id Of Scan (Example: "scanId":"D0000000000") |
ReasonId | Integer | No |
Id Of Reason
|
Description | String | No | Case Closing Description |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"ScanId": "D000000001",
"ReasonId": 1,
"Description": "string"
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
ReOpen Case By ScanId
https://api.sanctionscanner.com/api/Operations/ReOpenCaseByScanId
This service is used to reopen case. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Id Of Scan (Example: "scanId":"D0000000000") |
Description | String | No | Case Reopening Description |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"ScanId": "D000000001",
"Description": "string"
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Add Search To Safe List
https://api.sanctionscanner.com/api/Operations/SearchAddToSafeList
This service is used to add search result to safe list. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
https://appv2.sanctionscanner.com/CaseManagement/SafeList
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Scan Id Of Search (Example: D00000001) |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call is updated guid using the SearchAddToSafeList.
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"ScanId":"D0000000000"
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Delete Search From Safe List By Reference Number
https://api.sanctionscanner.com/api/Operations/DeleteFromSafeListByReferenceNumber
This service is used to remove search result from safe list. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ReferenceNumber | String | Yes | Reference Number Of Search |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call is updated guid using the DeleteFromSafeListByReferenceNumber.
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"ReferenceNumber":"************"
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Search Add To Safe List By DataId
https://api.sanctionscanner.com/api/Operations/SearchAddToSafeListByDataId
This service is used to add data to safe list. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ReferenceNumber | String | Yes | Scan Id Of Search (Example: D00000001) |
DataList | List Of DataList Class | Yes | You can find the details in the table below. |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
SSID | String | Yes | SSID (Unique Id Of Data) of related data in scan result |
Type | String | Yes | Type of related data in scan result (Ex. Values: Sanction, Wanted, Watchlist, PEP, SIP, Local) |
EntityType | String | Yes | EntityType of related data in scan result (Ex. Values: Individual, Corporate, Vessel, Aircraft) |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call is updated guid using the SearchAddToSafeListByDataId.
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"ReferenceNumber": "************",
"DataList" : [
{
"SSID" : "************",
"Type" : "Sanction",
"EntityType" : "Individual"
},
{
"SSID" : "************",
"Type" : "Pep",
"EntityType" : "Individual"
}
]
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Search Remove From Safe List By DataId
https://api.sanctionscanner.com/api/Operations/SearchRemoveFromSafeListByDataId
This service is used to remove data from safe list. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ReferenceNumber | String | Yes | Scan Id Of Search (Example: D00000001) |
DataList | List Of DataList Class | Yes | You can find the details in the table below. |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
SSID | String | Yes | SSID (Unique Id Of Data) of related data in scan result |
Type | String | Yes | Type of related data in scan result (Ex. Values: Sanction, Wanted, Watchlist, PEP, SIP, Local) |
EntityType | String | Yes | EntityType of related data in scan result (Ex. Values: Individual, Corporate, Vessel, Aircraft) |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call is updated guid using the SearchRemoveFromSafeListByDataId.
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"ReferenceNumber": "************",
"DataList" : [
{
"SSID" : "************",
"Type" : "Sanction",
"EntityType" : "Individual"
},
{
"SSID" : "************",
"Type" : "Pep",
"EntityType" : "Individual"
}
]
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Get My Organization Tags
https://api.sanctionscanner.com/api/Operations/GetMyOrganizationTags
This service allows you to list the tags in your organization. The “GET” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | Result Class |
Result Information. The following internal table describes the internal parameters. |
Parameter Name | Data Type | Description |
---|---|---|
TagGuidId | String | Guid Id Of Tag |
TagName | String | Name Of Tag |
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
GET /api/Operations/GetMyOrganizationTags
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": [
{
"TagGuidId": "*******",
"TagName": "*******",
},
{
"TagGuidId": "*******",
"TagName": "*******",
}
]
}
Add Tag To Search
https://api.sanctionscanner.com/api/Operations/AddTagToSearch
This service is used to set tags to a search. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
https://appv2.sanctionscanner.com/CaseManagement/Index
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Scan Id Of Search (Example: D00000001) |
TagGuidId | String | Yes | Guid Id Of Tag |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call is updated guid using the AddTagToSearch.
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"scanId":"D0000000000",
"TagGuidId": "*******"
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Remove Tag From Search
https://api.sanctionscanner.com/api/Operations/RemoveTagFromSearch
This service is used to remove tags from search. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Scan Id Of Search (Example: D00000001) |
TagGuidId | String | Yes | Guid Id Of Tag |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Message |
In the link above, a call is updated guid using the RemoveTagFromSearch.
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
{
"scanId":"D0000000000",
"TagGuidId": "*******"
}
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": null
}
Get Search Tags By ScanId
https://api.sanctionscanner.com/api/Operations/GetSearchTagsByScanId&ScanId=ScanId
This service allows you to list all the tags in your search. When calling for service, the "GET" method should be used. In addition, the "user name" and "password" information required for the service should be sent as "Authorization" information via the "title". Service call should be made as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
ScanId | String | Yes | Scan Id Of Search (Example: D00000001) |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | Result Class |
Result Information. The following internal table describes the internal parameters. |
Parameter Name | Data Type | Description |
---|---|---|
TagGuidId | String | Guid Id Of Tag |
TagName | String | Name Of Tag |
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Sample Service Response Codes
//Request
GET /api/Operations/GetSearchTagsByScanId?ScanId=
//Response
{
"HttpStatusCode": 200,
"IsSuccess": true,
"ErrorCode": null,
"ErrorMessage": null,
"ExtraInfo": null,
"Result": [
{
"TagGuidId": "*******",
"TagName": "*******",
},
{
"TagGuidId": "*******",
"TagName": "*******",
}
]
}
Monitoring Enable
https://api.sanctionscanner.com/api/Operations/MonitoringEnable
This service is used to set as Ongoing Monitoring status enabled to a search that you've performed. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
scanId | String | Yes | Scan Id Of Search (Example: D0000001) |
periodId | String | No |
Period Info (Default : 1)
|
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Information |
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.
Monitoring Disable
https://api.sanctionscanner.com/api/Operations/MonitoringDisable
This service is used to set as Ongoing Monitoring status disabled to a search that you've performed. The “POST” method should be used when making a service call. In addition, the “username” and “password” information required for the service should be sent via “header” as “Authorization” information. The service call should be done as follows;
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
username | String | Yes | Api Username Info |
password | String | Yes | Api Password Info |
Parameter Name | Data Type | Requirement | Description |
---|---|---|---|
scanId | String | Yes | Scan Id Of Search (Example: D0000001) |
Parameter Name | Data Type | Description |
---|---|---|
HttpStatusCode | Int |
Transaction Result Code 200: Success 400: Unsuccessful |
IsSuccess | Boolean |
Transaction Result True: Success False: Unsuccessful |
ErrorCode | String |
Error Code |
ErrorMessage | String |
Error Message |
ExtraInfo | String |
Extra Information |
Result | String |
Result Information |
The result of the call is a result and the status of the transaction is returned in response. In successful transactions , this status returns to 200, and in unsuccessful transactions it returns to 400.