Sentinel Compliance Platform API's Introduction
Description
Sentinel Compliance Platform (SCP) is bundled with several RESTful API’s that are available for both developer and client use. The API enables users to interact with SCP programmatically, providing a way to integrate SCP into custom applications and automating tasks. The proposed documentation was created to provide a way for incoming developers or inquiring clients the ability to learn and use the RESTful API’s effectively.
Summary
Sentinel Compliance Platform (SCP) RESTful API’s provides a flexible and powerful way to interact with its platform, allowing for automation of tasks, integrating SCP into custom applications, and accessing SCP functionality programmatically. The API’s adhere to RESTful API design principles and use standard HTTP methods (GET, POST, PUT, DELETE, etc.).
The documentation will primarily focus on the Platform directory. The API’s are segregated into sub directories based off of their functionality in relation to Sentinel Compliance Platform (SCP). These sub directories are the following:
Authentication →
Sentinel Compliance Platform uses an authentication token to authenticate requests. Each API request requires a token, which is provided via /api/auth endpoint.
Batch →
Batch file upload searches and review queue for batches provided through API’s to provide functionality to users.Search →
Conducting compliance searches (individual or organization) for inquires through API access. Compliance search reporting and continuous monitored screenings.
Functional Spec
The functional specification outlines the functionality that the API provides and how it can be used. The following are the key features of the SCP API:
Access to Sentinel Compliance Platform (SCP) functionality: The API provides access to the full range of SCP functionality, allowing developers to interact with SCP in a programmatic way.
Standardized protocol: The API adheres to RESTful API design principles, using standard HTTP methods to interact with SCP.
Request and response format: The API uses JSON for request and response payloads, providing a standard and flexible format for data exchange between the API and client applications.
Acceptance Criteria:
Documentation shall explain functionality of the API
Documentation shall include the path and method of the API
Documentation shall include (if applicable) the parameters required for the API
Documentation shall include (if applicable) the request body required for the API
Documentation shall include the responses back for the particular API
Technical Spec
The technical specification outlines the technical details of the API, including the API path and method, parameters, request body, and responses. The following is a sample technical specification for a SCP API endpoint in JSON:
Example JSON:
"/api/account/{accountId}": {
"put": {
"description": "Update an Account",
"parameters": [
{
"name": "accountId",
"in": "path",
"required": true,
"schema": {
"type": "string"
}
},
{
"name": "authorization",
"in": "header",
"schema": {
"type": "string"
}
}
],
"requestBody":{
"$ref": "#/components/requestBodies/putAccount"
},
"responses": {
"200": {
"description": "OK"
},
"401": {
"description": "Unauthorized"
},
"503": {
"description": "Service Unavailable"
}
}
}
},