GET | /clients/incomplete/count | Get the number of incomplete clients |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
DaysIncomplete | query | int | No | How many days should have elapsed before counting a Client as incomplete (defaults to 7 days).Set to zero to count all incomplete clients |
State | query | ClientState | No | Count clients that match the state specified (only PendingCompletion, or PendingVerification). |
IsValidateMe | query | bool | No | Count clients that match the IsValidateMe flag specified (defaults to true). |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Authentication | header, body | Authentication | Yes | The authentication credentials |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ApiUserId | header, body | string | Yes | The API User ID provided by us when you signed up to use our API. Can be provided in the request body, or as a header parameter (X-Api-User) |
ApiUserKey | header, body | string | Yes | The API User Key provided by us when you signed up to use our API. Can be provided in the request body, or as a header parameter (X-Api-Key) |
UserId | header, body | string | No | The User ID of the user making the request (e.g. a sub user). This is optional but can be used to associate API requests with a specific user, thereby allowing user permissions to be enforced. Can be provided in the body, or as a header parameter (X-User-Id). |
Undefined | |
PendingCompletion | |
PendingOcr | |
PendingVerification | |
Verified |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Data | form | CountIncompleteClientsData | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
NumberOfIncompleteClients | form | long | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ResponseStatus | form | ResponseStatus | No | The status of the response |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ErrorCode | form | string | No | |
Message | form | string | No | |
StackTrace | form | string | No | |
Errors | form | ArrayOfResponseError | No | |
Meta | form | Dictionary<string, string> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ErrorCode | form | string | No | |
FieldName | form | string | No | |
Message | form | string | No | |
Meta | form | Dictionary<string, string> | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /clients/incomplete/count HTTP/1.1 Host: api.sanctionssearch.com Accept: application/json
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"data":{"numberOfIncompleteClients":0,"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}}