# Borneo Borneo is a data security and privacy platform designed for sensitive data discovery and remediation. - **Category:** security & identity tools - **Auth:** API_KEY, OAUTH2 - **Composio Managed App Available?** No - **Tools:** 153 - **Triggers:** 0 - **Slug:** `BORNEO` - **Version:** 20260211_00 ## Tools ### Access scan iteration by id **Slug:** `BORNEO_ACCESS_SCAN_ITERATION_BY_ID` Retrieves detailed information about a specific scan iteration in the Borneo integration platform. This endpoint allows users to fetch the current status, results, and metadata associated with a particular scan iteration. It should be used when monitoring the progress of a scan, analyzing results, or troubleshooting integration workflows. The endpoint provides a snapshot of the scan iteration at the time of the request and may not reflect real-time updates if the scan is still in progress. It's particularly useful for auditing, reporting, and maintaining a history of scan operations within Borneo's automation and integration processes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `scanIterationId` | string | Yes | The unique resource ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Add discovered recipients **Slug:** `BORNEO_ADD_DISCOVERED_RECIPIENTS` Adds multiple discovered recipients to the system as confirmed recipients. This endpoint should be used when you have a list of previously discovered recipient IDs that you want to officially add to your recipient database. It's particularly useful for bulk operations where multiple recipients need to be added simultaneously. The endpoint accepts an array of unique UUIDs, allowing for efficient processing of multiple recipients in a single API call. Note that this endpoint only adds recipients; it does not provide any information about the recipients or perform any other actions beyond adding them to the system. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `discoveredRecipientIds` | array | Yes | Identifiers of the discovered recipients to add as recipients. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Archive discovered recipient **Slug:** `BORNEO_ARCHIVE_DISCOVERED_RECIPIENT` Archives a specific discovered recipient in the Borneo platform. This endpoint is used to move a discovered recipient's data into an archived state, which may be useful for compliance, data retention, or organizational purposes. It should be called when you need to store historical data about a recipient that has been identified through Borneo's data visibility and privacy automation processes. The endpoint uses a POST method, suggesting it may trigger backend processes to properly archive the recipient's data. Note that this operation might affect the visibility or accessibility of the recipient's data in other parts of the system. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `discoveredRecipientId` | string | Yes | Identifier of the discovered recipient. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create and schedule cloud resource scan **Slug:** `BORNEO_CREATE_AND_SCHEDULE_CLOUD_RESOURCE_SCAN` The createScan endpoint initiates a new scan operation in the Borneo integration platform, allowing users to configure and schedule data scans across various cloud resources. This powerful tool enables users to set up both one-time and recurring scans, with extensive customization options for resource selection, data inspection policies, and scan limits. It's particularly useful for compliance checks, sensitive data discovery, and regular security audits across cloud environments. The endpoint supports a wide range of resource types and provides flexible scheduling options, from immediate execution to complex cron-based recurring scans. Users should carefully consider the scan configuration to balance thoroughness with resource utilization, especially for large-scale environments. While highly versatile, users should note that some features may be resource-type dependent, and should refer to Borneo's documentation for specific connector and filter support. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `cron` | string ("*/30 * * * *" | "0 */1 * * *" | "0 */12 * * *" | "0 */4 * * *" | "0 */6 * * *" | "0 */8 * * *" | "0 0 * * *" | "0 0 * * 0" | "0 0 1 * *" | "0 0 1 1,4,7,10 *" | "0 0 1 1,7 *") | No | The cron schedule expression to use for a recurring scan. Only a fixed set of cron expressions can be used to run scans at 30 minute, 1 hour, 1 day, or 1 week intervals. | | `name` | string | No | The name of the scan. | | `scanType` | string ("full" | "sample") | No | The type of scan to perform, i.e. either full scan or sample scan. | | `scanFilter` | array | No | Filter conditions to apply to the scan. | | `connectorId` | string | No | The ID of the connector to use for the scan. The connector type must match the resource type. | | `resourceType` | string | No | The type of resource to scan. | | `scheduleType` | string ("cron" | "once") | Yes | A schedule type of "once" indicates that the scan will be executed once immediately at the time it is created or once as per the scheduled calendar time. A schedule type of "cron" creates a recurring scan that will be executed at the specified cron schedule. | | `resources__all` | boolean | No | Set this to `true` to determine the set of resources to scan based on the filter conditions in the `resources` property. If set to `false`, a static set of `resourceIds` must be specified. | | `resources__name` | array | No | Name | | `resources__tags` | array | No | Filter the resources which have teh tags | | `resources__region` | string | No | The region of the cloud account to which the resoure belongs. | | `resources__schema` | array | No | Filter the resources with the list of schemas for selected connector types | | `resources__search` | string | No | Free-text search on the resource name. | | `resources__teamId` | string | No | Slack Workspace id in Slack Enterprise Connector | | `resources__dataset` | array | No | Filter the resources with the list of datasetss for selected connector types | | `resources__driveId` | array | No | Filter the resources with the list of driveIds for gdrive connector types | | `resources__regions` | array | No | List of regions to which the resoure belongs to in that cloud account. | | `resources__teamUrl` | string | No | Slack Workspace URL in Slack Enterprise Connector | | `schedule__timezone` | string | No | time zone to be considered for the schedule | | `resources__database` | array | No | Filter the resources with the list of databaseses for selected connector types | | `resources__isPublic` | boolean | No | Filter the resources which are public. | | `resources__parentId` | string | No | Filter the resources which has the specified parent id. | | `resources__teamName` | string | No | Slack Workspace name in Slack Enterprise Connector | | `schedule__calendars` | array | No | List of schedules | | `resources__accountId` | string | No | The account ID of the cloud account to which the resoure belongs. E.g. a 12-digit AWS account ID. | | `resources__driveType` | array | No | Filter the resources with the list of driveTypes for gdrive connector types | | `resources__isPrivate` | boolean | No | Private channels, for Slack Enterprise Connector | | `resources__orgUnitId` | array | No | Filter the resources with the list of orgUnits for gdrive connector types | | `resources__spaceType` | array | No | Filter conlfluences based on type | | `resources__isArchived` | boolean | No | Filter the channels marked as archived for Slack connector types | | `resources__isExternal` | boolean | No | Filter the channels marked as external for Slack connector types | | `resources__resourceIds` | array | No | One or more resource IDs to return. | | `resources__spaceStatus` | array | No | Filter conlfluences based on status | | `resources__googleGroups` | array | No | Googlegroups | | `resources__resourceType` | string | No | Filter the resources based on the resource type. | | `resources__isUnencrypted` | boolean | No | Filter the resources which are un-unencrypted. | | `resources__infoTypes__ops` | string ("AND" | "OR") | No | Ops | | `resources__zendeskGroupId` | array | No | Zendeskgroupid | | `scanLimits__itemsPerBatch` | integer | No | Maximum number of item (records, objects, etc.) to scan per resource. Supported for sample scans on the following resource types: S3, DynamoDB, PostgreSQL, MySQL, Presto, MongoDB, BigQuery, Cassandra. | | `inspectionPolicy__infotypes` | array | No | List of infotypes to scan for. If empty, all enabled infotypes will be included. | | `inspectionPolicy__compliance` | array | No | List of infotype categories to scan for. All enabled infotypes included in the specified categories will be used in the scan. If `infotypes` is also specified, this list of infotype categories will be ignored. | | `scanLimits__samplePercentage` | integer | No | Percentage of data to scan per resource. Supported for full scans on the following resource types: S3, BigQuery. | | `inspectionPolicy__maskDetails` | boolean | No | If true, the matched tokens captured as part of the detailed scan results will be masked. If false, the raw, unmasked tokens will be captured. Use with caution. Only applicable if `detailed` scan results are enabled. | | `inspectionPolicy__collectTokens` | boolean | No | If true, the scan will capture details about every infotype match, including the matched token, and exact location of the token. If false, the scan will capture only aggregate results (a.k.a. "snapshot" results). | | `resources__infoTypes__infoTypes` | array | No | The list of infotypes to filter on. | | `resources__isSlackDirectMessages` | boolean | No | Fetch DMs, for Slack Enterprise Connector | | `scanLimits__sampleDurationMinutes` | integer | No | Sampledurationminutes | | `scanLimits__maxCumulativeDataSizeMb` | integer | No | Maximum data size to scan per resource in MB. Supported for full scans on the following resource types: PostgreSQL, MySQL. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create dashboard user **Slug:** `BORNEO_CREATE_DASHBOARD_USER` Creates a new dashboard user in the Borneo integration platform with specified roles, organizational access, and authentication settings. This endpoint allows for granular control over user permissions across different organizations and departments within the Borneo ecosystem. It supports integration with external identity providers (OKTA or GCP) for authentication. Use this endpoint when onboarding new users or updating existing user permissions. Note that while only the email is required, it's recommended to provide comprehensive role and organization information for proper access control. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | No | Name | | `email` | string | Yes | Email | | `roles` | array | No | Roles | | `filter__id` | string | No | Id | | `filter__type` | string ("GCP" | "OKTA") | No | Type | | `organisations` | array | No | Organisations | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create department with translations **Slug:** `BORNEO_CREATE_DEPARTMENT_WITH_TRANSLATIONS` Creates a new department in the Borneo integration platform. This endpoint allows you to add a department to the system with support for multilingual information. It's particularly useful when setting up the organizational structure within Borneo or when expanding to new regions requiring localized department names. The endpoint should be used when you need to establish a new department entity that other parts of the system can reference. It's important to note that this endpoint only creates the department and does not associate it with any specific workflows or integrations - those would need to be set up separately. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | No | Name | | `translations` | object | No | Translations | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create domain with polling frequency **Slug:** `BORNEO_CREATE_DOMAIN_WITH_POLLING_FREQUENCY` Creates a new domain within the Borneo integration platform, allowing for automatic polling and management of connected systems or applications. This endpoint is used to set up a new integration point with a specific name and polling frequency. It should be used when establishing a new connection or integration within the Borneo ecosystem. The endpoint is particularly useful for setting up automated data synchronization or workflow triggers between different business applications. It does not provide information about existing domains or modify existing ones; it is strictly for creating new domains. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | Name of the domain. | | `frequency` | string ("12h" | "1d" | "1w" | "30d" | "6h" | "manual") | Yes | Frequency of polling for a domain. Manual polling means that this domain will not be polled automatically. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create dpia for processing activity **Slug:** `BORNEO_CREATE_DPIA_FOR_PROCESSING_ACTIVITY` Creates a new Data Protection Impact Assessment (DPIA) for a specific processing activity in the Borneo application. This endpoint allows users to comprehensively assess and document privacy risks associated with data processing, including confidentiality, integrity, and availability risks. It should be used when initiating a new DPIA process or updating an existing one with detailed risk assessments and mitigation measures. The tool provides a structured approach to evaluating privacy concerns and ensuring compliance with data protection regulations. However, it does not automatically implement any risk mitigation measures; it only facilitates the assessment and documentation process. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `status` | string ("activated" | "draft") | Yes | The status of the DPIA. If a DPIA is saved as activated, several fields are required | | `createdAt` | integer | No | Createdat | | `updatedAt` | integer | No | Updatedat | | `translations` | object | No | Translations | | `integrity__impacts` | array | No | List of impacts that integrity risk can have. At least one element is necessary DPIA is saved as activated | | `integrity__threats` | array | No | List of threats that integrity risk can have. At least one element is necessary DPIA is saved as activated | | `processingActivityId` | string | Yes | Identifier of the processing activity for which we are creating a DPIA | | `additionalInformation` | string | No | Additionalinformation | | `availability__impacts` | array | No | List of impacts that availability risk can have. At least one element is necessary DPIA is saved as activated | | `availability__threats` | array | No | List of threats that availability risk can have. At least one element is necessary DPIA is saved as activated | | `integrity__plannedToms` | array | No | List of TOMs that are planned to be implemented to prevent integrity risk. At least one element is necessary DPIA is saved as activated | | `integrity__riskSources` | array | No | List of risk sources that integrity risk can have. At least one element is necessary DPIA is saved as activated | | `confidentiality__impacts` | array | No | List of impacts that confidentiality risk can have. At least one element is necessary DPIA is saved as activated | | `confidentiality__threats` | array | No | List of threats that confidentiality risk can have. At least one element is necessary DPIA is saved as activated | | `availability__plannedToms` | array | No | List of TOMs planned to be implemented and that applies to the availability risk. At least one element is necessary DPIA is saved as activated | | `availability__riskSources` | array | No | List of risk sources that availability risk can have. At least one element is necessary DPIA is saved as activated | | `integrity__impactsComment` | string | No | Comment to add additional information about the integrity impacts | | `integrity__threatsComment` | string | No | Comment to add additional information about the integrity threats | | `privacyFramework__consent` | string | No | Field to describe the measures to ensure that the consent of the data subjects has been obtained and how the given consent can be revoked Mandatory if DPIA is saved as activated and the lawfulness "consent_person_concerned" selected | | `additionalInformationFiles` | array | No | Additionalinformationfiles | | `integrity__baselineComment` | string | No | Comment to add additional information about the baseline risk of the integrity | | `integrity__implementedToms` | array | No | List of TOMs that are implemented to prevent integrity risk. At least one element is necessary DPIA is saved as activated | | `privacyFramework__accuracy` | string | No | Field to explain if the data processed is accurate, high quality and up-to-date Mandatory if DPIA is saved as activated | | `integrity__baselineSeverity` | string ("high" | "low" | "medium" | "very_high" | "very_low") | No | Represents the severity of a risk | | `privacyFramework__retention` | boolean | No | Is the retention period lawful and clearly defined? Mandatory if DPIA is saved as activated | | `availability__impactsComment` | string | No | Comment to add additional information about the impact | | `availability__threatsComment` | string | No | Comment to add additional information about the threat | | `confidentiality__plannedToms` | array | No | List of TOMs that are planned to be implemented to prevent confidentiality risk. At least one element is necessary DPIA is saved as activated | | `confidentiality__riskSources` | array | No | List of risk sources that confidentiality risk can have. At least one element is necessary DPIA is saved as activated | | `availability__baselineComment` | string | No | Comment to add additional information about the baseline risk of the availablity | | `availability__implementedToms` | array | No | List of implemented TOMs that applies to the availability risk. At least one element is necessary DPIA is saved as activated | | `integrity__baselineLikelihood` | string ("likely" | "limited" | "maximum" | "negligible" | "unlikely") | No | Baselinelikelihood | | `integrity__plannedTomsComment` | string | No | Comment to add additional information about planned TOMs to prevent integrity risk | | `integrity__riskSourcesComment` | string | No | Comment to add additional information about the integrity risk sources | | `availability__baselineSeverity` | string ("high" | "low" | "medium" | "very_high" | "very_low") | No | Represents the severity of a risk | | `integrity__residualRiskComment` | string | No | Comment to add additional information about the residual risk of the integrity | | `privacyFramework__transparency` | string | No | Field to describe what kind of notice information is given to data subjects about this processing, and how is it provided to the data subjects? Mandatory if DPIA is saved as activated | | `confidentiality__impactsComment` | string | No | Comment to add additional information about the confidentiality risk impacts | | `confidentiality__threatsComment` | string | No | Comment to add additional information about the confidentiality risk threats | | `integrity__residualRiskSeverity` | string ("high" | "low" | "medium" | "very_high" | "very_low") | No | Represents the severity of a risk | | `availability__baselineLikelihood` | string ("likely" | "limited" | "maximum" | "negligible" | "unlikely") | No | Baselinelikelihood | | `availability__plannedTomsComment` | string | No | Comment to add additional information about the planned TOMs | | `availability__riskSourcesComment` | string | No | Comment to add additional information about the availability risk sources | | `confidentiality__baselineComment` | string | No | Comment to add additional information about the baseline risk of the confidentiality | | `confidentiality__implementedToms` | array | No | List of TOMs that are implemented to prevent confidentiality risk. At least one element is necessary DPIA is saved as activated | | `availability__residualRiskComment` | string | No | Comment to add additional information about the residual risk of the availability | | `confidentiality__baselineSeverity` | string ("high" | "low" | "medium" | "very_high" | "very_low") | No | Represents the severity of a risk | | `integrity__implementedTomsComment` | string | No | Comment to add additional information about implemented TOMs to prevent integrity risk | | `integrity__residualRiskLikelihood` | string ("likely" | "limited" | "maximum" | "negligible" | "unlikely") | No | Residualrisklikelihood | | `availability__residualRiskSeverity` | string ("high" | "low" | "medium" | "very_high" | "very_low") | No | Represents the severity of a risk | | `privacyFramework__dataMinimisation` | string | No | Field to explain if the data collected adequate, relevant, and limited to what is necessary concerning the purposes for which it is processed Mandatory if DPIA is saved as activated | | `privacyFramework__retentionComment` | string | No | Field to add comment on the retention period | | `confidentiality__baselineLikelihood` | string ("likely" | "limited" | "maximum" | "negligible" | "unlikely") | No | Baselinelikelihood | | `confidentiality__plannedTomsComment` | string | No | Comment to add additional information about planned TOMs to prevent confidentiality risk | | `confidentiality__riskSourcesComment` | string | No | Comment to add additional information about the confidentiality risk sources | | `privacyFramework__additionalComment` | string | No | Field to add more information related to the privacy framework of the DPIA | | `privacyFramework__purposeLimitation` | string | No | Field to explain the clear, specific and legitimate purpose of conducting the processing activity. Mandatory if DPIA is saved as activated | | `availability__implementedTomsComment` | string | No | Comment to add additional information about the implemented TOMs | | `availability__residualRiskLikelihood` | string ("likely" | "limited" | "maximum" | "negligible" | "unlikely") | No | Residualrisklikelihood | | `confidentiality__residualRiskComment` | string | No | Comment to add additional information about the residual risk of the confidentiality | | `confidentiality__residualRiskSeverity` | string ("high" | "low" | "medium" | "very_high" | "very_low") | No | Represents the severity of a risk | | `privacyFramework__dataRightsExercised` | string | No | Field to describe how do data subjects exercise their data subject rights? Mandatory if DPIA is saved as activated | | `confidentiality__implementedTomsComment` | string | No | Comment to add additional information about implemented TOMs to prevent confidentiality risk | | `confidentiality__residualRiskLikelihood` | string ("likely" | "limited" | "maximum" | "negligible" | "unlikely") | No | Residualrisklikelihood | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create employee with json payload **Slug:** `BORNEO_CREATE_EMPLOYEE_WITH_JSON_PAYLOAD` Creates a new employee record in the Borneo integration platform. This endpoint allows you to add an employee to the system with various details such as personal information, job-related data, and organizational structure. It's primarily used when onboarding new employees or updating the system with employee information from external sources. The endpoint captures both mandatory fields (name, surname, createdBy) and optional fields for a comprehensive employee profile. It's particularly useful for HR systems integration, allowing synchronization with external APIs through the referenceId field. Note that while it collects employment dates, it doesn't automatically handle employee status changes or departures; these would likely require separate API calls or processes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `nif` | string | No | The NIF of the employee | | `name` | string | Yes | The name of the employee | | `email` | string | No | the email of the employee | | `endDate` | string | No | Date when the employee end to work in your company | | `manager` | string | No | employeeId of the employee who is manager of the employee | | `surname` | string | Yes | The surname of the employee | | `position` | string | No | The position of the employee in the company. | | `createdBy` | string | Yes | Createdby | | `startDate` | string | No | Date when the employee began to work in your company | | `department` | string | No | the department of the employee | | `referenceId` | string | No | Internal identifier to synchronize with external APIS | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create headquarter entry **Slug:** `BORNEO_CREATE_HEADQUARTER_ENTRY` Creates a new headquarters entry in the Borneo integration platform. This endpoint allows users to register the main office or primary location of a company or organization within the system. It captures essential information about the headquarters, including its name, address, and associated identifiers. Use this endpoint when setting up a new company profile or updating the primary business location. The endpoint ensures data consistency by enforcing specific formatting rules for each field. It's particularly useful for organizations managing multiple locations or integrating headquarters data with other business systems. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `city` | string | Yes | The locality of the headquarter | | `name` | string | Yes | The name of the headquarter | | `tomIds` | array | No | Tomids | | `address` | string | Yes | The address of the headquarter | | `country` | string | Yes | 2 letter code that identifies a country. | | `zipcode` | string | No | The zipcode of the headquarter | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create legal document entry **Slug:** `BORNEO_CREATE_LEGAL_DOCUMENT_ENTRY` Creates or uploads a new legal document in the Borneo integration platform with specified metadata. This endpoint allows users to add various types of legal documents, such as privacy policies or data processing agreements, to the system. It captures essential information about the document, including its location, type, applicable region, and discovery settings. Use this endpoint when you need to integrate new legal documents into your workflow or update existing ones with new versions. The tool is particularly useful for maintaining a centralized repository of legal documents across different regions and categories within your organization. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | Name | | `type` | string ("DATA_PROCESSING" | "PRIVACY_POLICY") | No | Type | | `region` | string | Yes | Region | | `source` | string | No | Source | | `documentLink` | string | Yes | Documentlink | | `isDiscoverInfotype` | boolean | Yes | Isdiscoverinfotype | | `fromDiscoveredDocumentId` | string | No | Fromdiscovereddocumentid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create new asset **Slug:** `BORNEO_CREATE_NEW_ASSET` Creates a new asset in the Borneo integration platform. This endpoint allows users to add various types of assets to their inventory, ranging from hardware and software applications to office furniture and documentation. It's primarily used when onboarding new resources or updating the asset registry. The endpoint captures essential information about each asset, including its type, location, and associated identifiers. It's particularly useful for organizations managing diverse asset portfolios across multiple locations. Note that while creating an asset, only the name and type are required, allowing for flexible asset management workflows. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | Name of the asset to create | | `type` | string ("applications" | "cloudServices" | "communications" | "dataInformation" | "externalStorage" | "filingRoom" | "furniture" | "hardware" | "hosting" | "other" | "paperDocumentation" | "printer" | "server" | "shredder" | "videoSurveillance") | Yes | Indicates the type of the asset. An asset can be one of the several options. | | `tomIds` | array | No | Tomids | | `createdAt` | integer | No | Createdat | | `locationId` | string | No | Locationid | | `locationType` | string ("external" | "office" | "remote") | No | Locationtype | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create new infotype category **Slug:** `BORNEO_CREATE_NEW_INFOTYPE_CATEGORY` Creates a new infotype category in the Borneo integration platform, allowing users to organize and group related sensitive data types. This endpoint is used to establish a structured hierarchy for managing various infotypes, such as PII, PFI, and PHI, enhancing data protection and compliance efforts. The created category serves as a container for specific infotypes, facilitating efficient data classification and management within the Borneo ecosystem. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `infotypes` | array | Yes | The list of infotypes that belong to this category. | | `description` | string | No | Description of the infotype category. | | `categoryLabel` | string | Yes | The name of the infotype category. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create processing activity **Slug:** `BORNEO_CREATE_PROCESSING_ACTIVITY` Creates a new processing activity in the Borneo integration platform. This endpoint allows users to define and configure detailed attributes of a data processing activity, including its purpose, legal basis, data sources, subjects, retention policies, and organizational roles. It's essential for organizations to document their data processing activities for compliance with data protection regulations. Use this endpoint when setting up a new data processing workflow or updating existing processes in your organization's data management strategy. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | Name of the processing activity | | `owner` | string | No | Owner | | `active` | boolean | Yes | Flag to create the processing activity as activated or draft | | `assets` | array | No | List assets ids related to the processing activity. | | `modelId` | string | No | Modelid | | `purpose` | string | No | Purpose | | `language` | string ("ar" | "de" | "en" | "es" | "es-EC" | "es-MX" | "fr" | "hi" | "it" | "ja" | "pt" | "zh") | No | Language | | `createdAt` | integer | No | Createdat | | `dataTypes` | array | No | Datatypes | | `infotypes` | array | No | List of info types related with the processing activity. | | `updatedAt` | integer | No | Updatedat | | `recipients` | array | No | List of recipients related with the processing activity. | | `companyRole` | array | No | Companyrole | | `dataSources` | array | No | Datasources | | `departments` | array | No | List departments related with the processing activity. | | `lawfulBasis` | array | No | List of Lawfulness types affected by a processing activity | | `dataSubjects` | array | No | List of Data Subjects affected by the processing activity | | `isDataStored` | boolean | No | Indicates if you store the data. | | `translations` | object | No | Translations | | `contactPerson` | string | No | Contact person for the processing activity. | | `additionalInfo` | string | No | Text to add more information about the processing activity | | `infotypeVolume` | string ("0-1000" | "1000-10000" | "10000-100000" | "100000+") | No | Ranges of the processed infotype volume. | | `managementMethods` | array | No | Managementmethods | | `infotypeCategories` | array | No | List of info types categories related with the processing activity. | | `showOnRopaDocument` | boolean | No | Showonropadocument | | `additionalInfoFiles` | array | No | List of uploaded file ids. | | `processingFrequency` | string ("is_systematic" | "not_systematic") | No | Data processing frequency. | | `dataFlowRelationships` | array | No | Dataflowrelationships | | `retentionPeriod__unit` | string ("day" | "month" | "week" | "year") | No | Unit of time that is used for retention period | | `retentionPeriodComment` | string | No | Retentionperiodcomment | | `retentionPeriod__value` | integer | No | Value | | `areAccessRequestsManaged` | boolean | No | Indicates if the data subject access requests are managed. | | `processingFrequencyComment` | string | No | Processingfrequencycomment | | `processingActivitiesAsDataSources` | array | No | Processingactivitiesasdatasources | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create processing activity threshold **Slug:** `BORNEO_CREATE_PROCESSING_ACTIVITY_THRESHOLD` Creates a new threshold for a specific data processing activity in the context of LOPDP (Law on Personal Data Protection) compliance. This endpoint is used to define and assess various risk factors associated with data processing activities. It allows for the creation of detailed risk profiles by setting multiple boolean flags for different aspects of data processing, such as systematic personal assessment, large-scale observation, and handling of sensitive data. The threshold can be saved as a draft or activated immediately. This tool is essential for organizations to evaluate and document their data processing activities for compliance purposes and risk management. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `status` | string ("activated" | "draft") | No | Status of the threshold. Can be draft or activated. | | `comment` | string | No | Additional information related to the Threshold | | `additionalComment` | boolean | No | Additionalcomment | | `processingActivityId` | string | Yes | Identifier of the processing activity for which the threshold will be created | | `largeScaleObservation` | boolean | No | Largescaleobservation | | `sensitiveOrSpecialData` | boolean | No | Sensitiveorspecialdata | | `rightsRiskProcessingData` | boolean | No | Rightsriskprocessingdata | | `freedomRiskProcessingData` | boolean | No | Freedomriskprocessingdata | | `innovativeTechnologiesUsed` | boolean | No | Innovativetechnologiesused | | `processingPersonalDataRisk` | boolean | No | Processingpersonaldatarisk | | `specialCategoryDataProcessed` | boolean | No | Specialcategorydataprocessed | | `systematicPersonalAssessment` | boolean | No | Systematicpersonalassessment | | `processingVulnerableDataSubject` | boolean | No | Processingvulnerabledatasubject | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create recipient with details **Slug:** `BORNEO_CREATE_RECIPIENT_WITH_DETAILS` Creates a new recipient in the Borneo integration platform. This endpoint is used to register and manage detailed information about entities that receive or process data within the system. It captures essential details for compliance with data protection regulations, including the recipient's role, location, data storage information, and associated legal documents like Data Processing Agreements (DPAs). The endpoint is particularly useful for organizations managing complex data ecosystems with multiple partners, vendors, or internal departments. It should be used when onboarding new data recipients or updating existing recipient information to maintain accurate records for auditing and compliance purposes. Note that while many fields are optional, providing comprehensive information enhances the system's ability to manage data flow and compliance effectively. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dpa` | string | No | The url to the DPA of the recipient | | `name` | string | Yes | Name of the recipient. Has to be unique, 2 different recipients can"t have the same name. | | `role` | array | No | Role | | `state` | string ("AK" | "AL" | "AR" | "AZ" | "CA" | "CO" | "CT" | "DC" | "DE" | "FL" | "GA" | "HI" | "IA" | "ID" | "IL" | "IN" | "KS" | "KY" | "LA" | "MA" | "MD" | "ME" | "MI" | "MN" | "MO" | "MS" | "MT" | "NC" | "ND" | "NE" | "NH" | "NJ" | "NM" | "NV" | "NY" | "OH" | "OK" | "OR" | "PA" | "RI" | "SC" | "SD" | "TN" | "TX" | "UT" | "VA" | "VT" | "WA" | "WI" | "WV" | "WY") | No | 2 letter code that identifies the state of the recipient. It only applies when the recipient country is US | | `status` | string ("archived" | "validated") | Yes | The status of the recipient. Can be archived or validated. | | `country` | string | No | 2 letter code that identifies a country. | | `dpaFiles` | array | No | List of uploaded file ids. | | `createdAt` | integer | No | Createdat | | `dpaStatus` | string ("attached" | "notRequired" | "requested") | No | The status of the DPA of the recipient. Attached if the DPA is provided. Not required when it"s not necessary to provide the information. Requested when we ask for the DPA and we are waiting for it. | | `updatedAt` | integer | No | Updatedat | | `categories` | array | No | list of recipient category | | `businessName` | string | No | Business name of the recipient | | `recipientState` | string ("active" | "assessment") | No | Recipientstate | | `subProcessorIds` | array | No | Subprocessorids | | `recipientModelId` | string | No | Identifier of the Recipient Model in case that the Recipient is created bases in a Recipient Model | | `dataStorageLocation` | array | Yes | List of countries where the data related to this recipient are stored | | `recipientWarranties` | array | Yes | List of lawful basis types that applies to the recipient. | | `fromDiscoveredRecipientId` | string | No | Fromdiscoveredrecipientid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Create threshold for processing activity **Slug:** `BORNEO_CREATE_THRESHOLD_FOR_PROCESSING_ACTIVITY` Creates a new threshold for a specific data processing activity in the Borneo integration platform. This endpoint is used to define and set various characteristics and risk factors associated with a data processing activity, which is crucial for privacy compliance and risk assessment. The threshold creation process captures detailed information about the nature, scope, and potential impact of data processing, allowing organizations to evaluate and manage privacy risks effectively. Use this endpoint when setting up new data processing activities or updating the risk profile of existing ones. The created threshold can be in either 'draft' or 'activated' status, allowing for review before finalizing. Note that while many parameters are optional, providing comprehensive information ensures a more accurate risk assessment. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `status` | string ("activated" | "draft") | No | Status of the threshold. Can be draft or activated. | | `comment` | string | No | Additional information related to the Threshold | | `blacklist` | boolean | No | Indicates if the data processing is included in a black list | | `createdAt` | integer | No | Createdat | | `updatedAt` | integer | No | Updatedat | | `translations` | object | No | Translations | | `processingActivityId` | string | Yes | Identifier of the processing activity for which the threshold will be created | | `classifyingDataSubject` | boolean | No | Indicates if this data processing is assessing or classifying data subjects | | `automatedDecisionMaking` | boolean | No | Indicates if there is automated decision-making with legal effect, or similarly significant effect involved | | `largeScaleDataProcessing` | boolean | No | Indicates if is a large scale data processing | | `innovativeTechnologiesUsed` | boolean | No | Indicates if there are innovative technologies used | | `matchingMergingRecordsInvolved` | boolean | No | Indicates if there is matching or merging of the records involved | | `processingVulnerableDataSubject` | boolean | No | Indicates if there is processing of data of vulnerable data subjects | | `systematicMonitoringDataSubject` | boolean | No | Indicates if there is systematic monitoring of data subjects involved | | `largeScaleProcessingSensitiveData` | boolean | No | Indicates if the data processing is large scale processing of sensitive data. | | `monitoringPubliclyAccessibleAreas` | boolean | No | Indicates if the data processing is systematic and large scale monitoring of publicly accessible areas involved. | | `processingConfidentialSensitiveData` | boolean | No | Indicates if there is processing of confidential or sensitive data | | `preventDataSubjectsExercisingTheirRights` | boolean | No | Indicates if the data processing prevents the data subjects from exercising their rights, using a service or performing a contract | | `extensiveAutomatedEvaluationCharacteristics` | boolean | No | Indicates if the data processing involve any systematic, extensive and automated evaluation of personal characteristics with effect for the data subjects. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete asset by id **Slug:** `BORNEO_DELETE_ASSET_BY_ID` The DeleteAsset endpoint removes a specific asset from the Borneo integration platform. This operation is used when an asset needs to be permanently deleted from the system, such as when it's no longer relevant or has been decommissioned. The deletion is irreversible, so it should be used with caution. This endpoint is particularly useful for maintaining an up-to-date asset inventory, cleaning up obsolete data, or managing system resources. It's important to note that deleting an asset may have implications on related data or integrations, so users should ensure that the asset is no longer needed before proceeding with deletion. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `assetId` | string | Yes | Identifier of the asset | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete category by label **Slug:** `BORNEO_DELETE_CATEGORY_BY_LABEL` Deletes a specific category from the Borneo integration platform using its unique label. This endpoint should be used when you need to remove an entire category and all its associated data from the system. It's particularly useful for cleaning up outdated or unnecessary categories. Be cautious when using this endpoint, as the deletion is permanent and cannot be undone. This operation will fail if the specified category doesn't exist or if there are any dependencies preventing its deletion. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `categoryLabel` | string | Yes | The name of the infotype category. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete dashboard report by id **Slug:** `BORNEO_DELETE_DASHBOARD_REPORT_BY_ID` Deletes a specific dashboard report from the Borneo integration platform. This endpoint should be used when you need to permanently remove a dashboard report that is no longer needed or relevant. It's important to note that this action is irreversible, and once a report is deleted, it cannot be recovered. Use this endpoint with caution, ensuring that the report is no longer required before deletion. The endpoint does not return the deleted report data, so make sure to retrieve any necessary information before deletion if needed. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dashboardReportId` | string | Yes | Dashboardreportid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete data breach by id **Slug:** `BORNEO_DELETE_DATA_BREACH_BY_ID` Deletes a specific data breach evaluation record from the Borneo system. This endpoint should be used when an organization needs to remove an evaluation record, typically in cases where the record is no longer relevant, contains errors, or needs to be purged for compliance reasons. The operation is irreversible, so it should be used with caution. This tool is part of Borneo's DataBreachManagement functionality, supporting the platform's data protection and privacy management capabilities. It helps maintain an accurate and up-to-date record of data breach evaluations, which is crucial for regulatory compliance and risk management. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dataBreachId` | string | Yes | Databreachid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete department by id **Slug:** `BORNEO_DELETE_DEPARTMENT_BY_ID` Deletes a specific department from the Borneo platform using its unique identifier. This endpoint should be used when you need to remove a department that is no longer relevant or has been decommissioned. It's important to note that this operation is irreversible and will permanently remove all data associated with the specified department. Use this endpoint with caution, as it may impact resource management and organizational structure within the Borneo context. Before deletion, ensure that all necessary data has been backed up or transferred to other relevant departments if required. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `departmentId` | string | Yes | Identifier of the department. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete domain by id **Slug:** `BORNEO_DELETE_DOMAIN_BY_ID` Deletes a specific domain from the Borneo integration platform. This endpoint permanently removes all data and configurations associated with the specified domain. Use this operation with caution, as it cannot be undone. It should be used when a domain is no longer needed or when cleaning up unused resources. This operation may have cascading effects on related integrations or workflows, so ensure all dependencies are considered before deletion. The API will likely require appropriate authentication and authorization to perform this sensitive operation. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `domainId` | string | Yes | Identifier of the domain. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete dpia by id **Slug:** `BORNEO_DELETE_DPIA_BY_ID` Deletes a specific Data Protection Impact Assessment (DPIA) from the Borneo system. This endpoint should be used when a DPIA is no longer needed or relevant, such as when a project has been completed or cancelled, or when the assessment needs to be removed due to policy changes. The operation is irreversible, so it should be used with caution. Once deleted, the DPIA and its associated data cannot be recovered through the API. This endpoint is part of Borneo's data privacy management features, allowing organizations to maintain an up-to-date repository of their DPIAs. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dpiaId` | string | Yes | Identifier of the DPIA | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete employee by id **Slug:** `BORNEO_DELETE_EMPLOYEE_BY_ID` Deletes an employee record from the Borneo system using the specified employee ID. This endpoint should be used when an employee leaves the organization or when their record needs to be permanently removed from the system. Once deleted, the employee data cannot be recovered through the API, so use this endpoint with caution. It's recommended to archive or backup employee data before deletion if retention is required for compliance or record-keeping purposes. This operation is final and irreversible within the Borneo platform. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `employeeId` | string | Yes | Identifier of the employee | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete headquarters by id **Slug:** `BORNEO_DELETE_HEADQUARTERS_BY_ID` Deletes a specific headquarters record from the Borneo system. This endpoint should be used when you need to permanently remove a headquarters entry from your organization's data. It's particularly useful for cleaning up obsolete or erroneous headquarters data. Exercise caution when using this endpoint, as the deletion is irreversible and will remove all associated data for the specified headquarters. Ensure you have the correct headquarterId before proceeding with the deletion to avoid unintended data loss. This operation may have cascading effects on related data, such as employee records or location-based configurations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `headquarterId` | string | Yes | The identifier of the headquarter | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete legal document by id **Slug:** `BORNEO_DELETE_LEGAL_DOCUMENT_BY_ID` Deletes a specific legal document from the Borneo platform using its unique identifier. This endpoint should be used when a document needs to be permanently removed from the system, such as when it's no longer relevant, outdated, or to comply with data retention policies. It's important to note that this operation is irreversible and should be used with caution. The deletion process ensures compliance with GDPR and FedRAMP standards, maintaining a secure audit trail of the action. Before deletion, ensure that all necessary backups or archival processes have been completed, as the document will no longer be accessible through the system after this operation. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `documentId` | string | Yes | Documentid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete lopdp threshold by id **Slug:** `BORNEO_DELETE_LOPDP_THRESHOLD_BY_ID` This endpoint deletes a specific LopdP (Local Public Data Protection) threshold from the Borneo integration platform. It is used to remove outdated, incorrect, or no longer applicable thresholds related to data protection regulations. The deletion is permanent and cannot be undone, so it should be used with caution. This endpoint is particularly useful when updating compliance settings or when certain thresholds are no longer relevant due to changes in regulations or business processes. It should not be used for temporary disabling of thresholds; instead, use it only when the threshold needs to be completely removed from the system. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `lopdpThresholdId` | string | Yes | Identifier of the Threshold | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete processing activity by id **Slug:** `BORNEO_DELETE_PROCESSING_ACTIVITY_BY_ID` Deletes a specific processing activity from the Borneo integration platform. This endpoint should be used when you need to permanently remove a data processing activity that is no longer required or valid. It's important to note that this action is irreversible, and once a processing activity is deleted, it cannot be recovered. Use this endpoint with caution, as it may impact existing data flows or integrations that depend on the deleted activity. The endpoint does not return the deleted data; it typically returns a success status if the deletion was completed successfully. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `processingActivityId` | string | Yes | Identifier of the Processing Activity | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete recipient by id **Slug:** `BORNEO_DELETE_RECIPIENT_BY_ID` Deletes a specific recipient from the Borneo integration platform. This endpoint should be used when you need to permanently remove a recipient's information from the system, such as when a contact is no longer valid or when correcting erroneous entries. The operation is irreversible, so it should be used with caution. Once a recipient is deleted, any associated data or integration settings for that recipient will also be removed. This endpoint is particularly useful for maintaining data hygiene and complying with data retention policies. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `recipientId` | string | Yes | Identifier of the Recipient | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete tag from resource **Slug:** `BORNEO_DELETE_TAG_FROM_RESOURCE` The DeleteTags endpoint removes specified tags from resources in the Borneo integration platform. It allows users to delete tags based on their key, and optionally, their value, from a set of resources defined either by a filter or a list of resource IDs. This endpoint is useful for maintaining clean and organized resource tagging, especially when tags become obsolete or need to be updated en masse. It's particularly helpful for bulk tag removal across multiple resources or resource types. However, users should exercise caution as tag deletion is irreversible and may affect resource management and organization within the Borneo platform. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `tagKey` | string | Yes | Tagkey | | `tagValue` | string | No | Tagvalue | | `tagResources` | object | Yes | Tagresources | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Delete threshold by id **Slug:** `BORNEO_DELETE_THRESHOLD_BY_ID` Deletes a specific threshold from the Borneo integration platform. This endpoint should be used when you need to remove a threshold that is no longer required for monitoring or alerting purposes within your integrations. It permanently removes the threshold configuration from the system, so use with caution. This operation cannot be undone, and once a threshold is deleted, any associated alerts or monitoring rules will cease to function. Ensure that the threshold is no longer needed before deletion to avoid disrupting active monitoring processes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `thresholdId` | string | Yes | Identifier of the Threshold | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Disable dashboard user by username **Slug:** `BORNEO_DISABLE_DASHBOARD_USER_BY_USERNAME` Disables a specified user account in the Borneo dashboard, preventing further access to the system. This endpoint should be used when an administrator needs to revoke a user's access to the Borneo integration platform, such as when an employee leaves the organization or their role changes. The operation is not reversible through this endpoint, so it should be used with caution. Note that disabling a user does not delete their account or associated data; it only restricts their ability to log in and use the dashboard. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `username` | string | Yes | Username | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Download dashboard report **Slug:** `BORNEO_DOWNLOAD_DASHBOARD_REPORT` The DownloadDashboardReport endpoint allows users to download specific types of dashboard reports from the Borneo integration platform. This POST endpoint is designed to generate and retrieve comprehensive reports related to privacy operations, data discovery, and data flow within an organization's systems. It should be used when detailed insights into data management, privacy compliance, or data flow visualizations are required. The endpoint is particularly useful for privacy officers, data analysts, or system administrators who need to review or present aggregated data on the organization's data handling practices. Note that the report generation process may take some time depending on the complexity and amount of data being analyzed, so users should be prepared for a potential delay before receiving the downloaded report. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `reportType` | string ("DATA_DISCOVERY_DASHBOARD" | "PRIVACY_OPS_DASHBOARD" | "PRIVACY_OPS_DATA_FLOW") | Yes | Reporttype | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Download dashboard report edition **Slug:** `BORNEO_DOWNLOAD_DASHBOARD_REPORT_EDITION` Downloads a specific dashboard report edition from the Borneo integration platform. This endpoint allows users to retrieve a particular version or iteration of a dashboard report by providing its unique identifier. It should be used when a user needs to access or save a specific report edition, perhaps for archival purposes, offline analysis, or to compare different versions of a report. The endpoint accepts a POST request with a JSON payload containing the report edition ID. It's important to note that this tool only handles the download process and does not provide functionalities for listing available reports, creating new reports, or modifying existing ones. Users should ensure they have the correct reportEditionId before making the request, as the schema does not specify any error handling for invalid IDs. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `reportEditionId` | string | Yes | Reporteditionid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Enable dashboard user **Slug:** `BORNEO_ENABLE_DASHBOARD_USER` Enables dashboard access for a specified user in the Borneo integration platform. This endpoint is used to grant or restore a user's ability to view and interact with dashboards within the system. It should be called when an administrator needs to activate a user's dashboard privileges, such as after initial account creation or if access was previously revoked. The endpoint only handles enabling access and does not provide information about the user's current access status or other account details. Note that this operation does not create a new user account; it assumes the specified username already exists in the system. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `username` | string | Yes | Username | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Evaluate data breach impact **Slug:** `BORNEO_EVALUATE_DATA_BREACH_IMPACT` This endpoint allows users to evaluate and document details of a data breach incident. It is used to capture comprehensive information about a breach, including notifications made, affected parties, and an overall assessment. The endpoint supports saving evaluations as drafts, enabling users to revisit and complete the documentation process over multiple sessions if needed. The tool should be used when there's a need to record and assess the impact and response to a data breach, whether it's a new incident or an update to an existing evaluation. It's particularly useful for compliance purposes, helping organizations track their breach notification efforts and maintain detailed records of each incident. It's important to note that this endpoint does not automatically notify authorities or affected parties; it merely records whether such notifications have been made. Users should ensure they follow appropriate breach notification procedures separately from using this tool. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `role` | string ("controller" | "independent_controller" | "joint_controller" | "processor" | "sub_processor") | No | Role of the recipient. | | `evaluation` | string | No | Evaluation | | `saveAsDraft` | boolean | Yes | Saveasdraft | | `dataBreachId` | string | Yes | Identifier of the DataBreach | | `reportLanguage` | string ("ar" | "de" | "en" | "es" | "es-EC" | "es-MX" | "fr" | "hi" | "it" | "ja" | "pt" | "zh") | No | Reportlanguage | | `companiesAffected` | string | No | Companiesaffected | | `processorNotified` | boolean | No | Processornotified | | `dataBreachLocation` | string ("ourOrganisation" | "thirdPartyProcessor") | No | Databreachlocation | | `processorsInvolved` | string | No | Processorsinvolved | | `authoritiesNotified` | boolean | No | Authoritiesnotified | | `dataBreachController` | string | No | Databreachcontroller | | `dataSubjectsNotified` | boolean | No | Datasubjectsnotified | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Export filtered leaf resources **Slug:** `BORNEO_EXPORT_FILTERED_LEAF_RESOURCES` The listLeafResources endpoint exports a comprehensive list of leaf resources in the Borneo integration platform, allowing for extensive filtering, sorting, and detailed information retrieval. It's designed to facilitate data discovery, classification, and management across various cloud providers and services. This endpoint is particularly useful for conducting audits, managing data governance, or preparing reports on resource usage and sensitive data distribution across the organization's digital landscape. The function supports a wide range of filtering options, enabling precise querying based on resource attributes, metadata, and detected sensitive information. Users can customize the output by sorting results and requesting detailed column-level information on detected infotypes. While powerful, users should be mindful of potential performance impacts when requesting detailed information or using complex filters on large datasets. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `detailed` | boolean | No | Set to `true` if the results exported to have detailed column level information of the detected infotypes. | | `sourceType` | string | No | Filter resource based on the source type. eg: "MYSQL", "RDS_MYSQL", "S3", "PRESTO", etc. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__region` | array | No | One or more cloud provider regions. | | `filter__schema` | array | No | List tables from a specific schema. Supported for the following resource types: Presto. | | `filter__search` | string | No | Free-text search on the resource name. | | `filter__status` | array | No | Filter the resources based on list of status. | | `filter__account` | array | No | One or more cloud provider account IDs. | | `filter__dataset` | array | No | List tables from a specific dataset. Supported for on the following resource types: BigQuery. | | `filter__driveId` | array | No | List drives from a specific driveId. Supported for the following resource types: Gdrive. | | `filter__noOwner` | boolean | No | Include only resources that have not been assigned an owner. | | `filter__scanned` | boolean | No | Include only resources that have been scanned. | | `filter__database` | array | No | List tables from a specific database. Supported for the following resource types: (RDS) PostgreSQL, (RDS) MySQL, MongoDB. | | `filter__hasOwner` | boolean | No | Include only resources that have been assigned an owner. | | `filter__instance` | array | No | One or more resource IDs of the instances to which the resources belong, i.e. the parent resource ID. | | `filter__parentId` | string | No | Filter the resources which has the specified parent ID. | | `filter__driveType` | array | No | List drives from a specific drive type. Supported for the following resource types: Gdrive. | | `filter__firstSeen` | object | No | Set of conditions for comparing two timestamps. | | `filter__orgUnitId` | array | No | List orgUnits from a specific orgUnitIds. Supported for the following resource types: Gdrive. | | `filter__spaceType` | array | No | Filter conlfluences based on type | | `filter__categories` | array | No | Filter the resources matching with the list of categories. | | `filter__resourceId` | array | No | Filter the resources with the specified resource IDs. | | `filter__spaceStatus` | array | No | Filter conlfluences based on status | | `filter__resourceTags` | array | No | Filter the resources based on tags | | `filter__resourceType` | array | No | Filter the resources which can be scanned by Borneo. | | `filter__severityScore` | array | No | Filter the resources based on the assigned risk severity score; "critical" = 4, "high" = 3, "medium" = 2, "low" = 1. | | `filter__classification` | array | No | Filter the resources matching with the list of classifications. | | `filter__infoTypes__ops` | string ("AND" | "OR") | No | Ops | | `filter__infoTypes__infoTypes` | array | No | The list of infotypes to filter on. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Export insight page using scanid **Slug:** `BORNEO_EXPORT_INSIGHT_PAGE_USING_SCAN_ID` The ExportPageInsight endpoint allows users to export filtered inspection results from a specific scan in the Borneo integration platform. This tool is particularly useful for retrieving and analyzing detailed information about scanned pages, resources, and detected info types. It provides extensive filtering capabilities to customize the exported data according to various criteria such as resource types, user associations, file types, and detection confidence levels. The endpoint should be used when a comprehensive export of scan results is needed, especially for further analysis or reporting purposes. It's important to note that while the filtering options are extensive, the performance may be affected when exporting large datasets with multiple complex filters applied simultaneously. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `scanId` | string | Yes | The unique scan ID. | | `detailed` | boolean | No | Set to `true` if the results exported to have detailed column level information of the detected infotypes with masked tokens if captured. | | `filter__pageId` | string | No | Unique page ID. Only applicable to page-level results. | | `filter__scanId` | string | No | Unique scan ID. | | `filter__search` | string | No | Free-text search on the resource name. | | `filter__status` | array | No | Status | | `filter__categories` | array | No | infotype categories | | `filter__userEmails` | array | No | Useremails | | `filter__resourceIds` | array | No | One or more resource IDs for which to retrieve results. Only applicable to page-level results. | | `filter__resourceType` | string | No | Resource type to filter results by. | | `filter__fileExtension` | array | No | Fileextension | | `filter__infoTypes__ops` | string ("AND" | "OR") | No | Ops | | `filter__scanIterationId` | string | No | Unique scan iteration ID to fetch results for a specific run of | | `filter__infotypeConfidence` | array | No | Infotypeconfidence | | `filter__infoTypes__infoTypes` | array | No | The list of infotypes to filter on. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Export inventory resource list **Slug:** `BORNEO_EXPORT_INVENTORY_RESOURCE_LIST` Exports a filtered and sorted list of inventory resources from the Borneo integration platform. This endpoint allows for extensive customization of the exported data, including pagination, field selection, sorting, and filtering based on various criteria such as account, region, resource type, and tags. It also provides options to include aggregated statistics from child resources, violation metrics, and framework exception counts. Use this endpoint when you need to retrieve a comprehensive, customized view of your inventory resources for analysis, reporting, or integration with other systems. The exported data can be further processed or used for compliance, resource management, or security auditing purposes. Note that the response may be paginated for large result sets, requiring multiple API calls to retrieve all data. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `select` | array | No | A list of property names to return in the response. If not specified, all resource properties will be returned. | | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | Optional "nextToken" value from the last API response. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__hasPii` | boolean | No | Include only resources that have a high likelihood of containing PII based on the resource metadata. | | `filter__region` | string | No | The region of the cloud account to which the resoure belongs. | | `filter__search` | string | No | Free-text search on the resource name. | | `filter__noOwner` | boolean | No | Include only resources that have not been assigned an owner. | | `filter__regions` | array | No | List of regions to which the resoure belongs to in that cloud account. | | `filter__hasOwner` | boolean | No | Include only resources that have been assigned an owner. | | `filter__parentId` | string | No | The parent Id of the resource. E.g. Borneo-specific GCP subscription ID for GCP resources | | `filter__accountId` | string | No | The account ID of the cloud account to which the resoure belongs. E.g. a 12-digit AWS account ID. | | `filter__dataRisks` | array | No | Filter the resources that has data risks. | | `filter__firstSeen` | object | No | Set of conditions for comparing two timestamps. | | `filter__resourceIds` | array | No | One or more resource IDs to return. | | `filter__resourceTags` | array | No | Filter the resources based on tags | | `filter__resourceType` | string | No | Filter the resources based on the resource type. | | `filter__severityScore` | array | No | Filter the resources based on the assigned risk severity score; "critical" = 4, "high" = 3, "medium" = 2, "low" = 1. | | `filter__classification` | array | No | Filter the resources based on classification and are non-compliant. eg "PII_L1", "PII_L2", "PII_L3". Custom added classifications is also supported. | | `include__violationMetrics` | boolean | No | Include violation count by severity for resource and child resources. | | `filter__hideBorneoResources` | boolean | No | Whether to hide resources that are part of the Borneo data plane. | | `filter__dataSourceCategories` | array | No | Filter the resources based on the data source category Current supported values: AWS_DATA_STORES, GCP_DATA_STORES, STANDALONE_DATA_STORES, CLOUD_APPLICATIONS, DISCOVERED_APPLICATIONS | | `filter__scannableResourceTypes` | boolean | No | Filter the resources that are scannable | | `include__frameworkExceptionsCount` | boolean | No | Include framework exceptions count for the resource and its children | | `include__childResourceStats__scans` | boolean | No | Include aggregate scan stats from child resources. | | `include__childResourceStats__dataSize` | boolean | No | Include aggregate data size stats from child resources. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Export processing activities list **Slug:** `BORNEO_EXPORT_PROCESSING_ACTIVITIES_LIST` This endpoint exports a filtered list of processing activities in specified formats and languages. It allows users to retrieve data about various data processing activities, which can be customized using multiple filter criteria. The export can be generated in CSV, PDF, or DOC formats, supporting multiple languages for localization. This tool is particularly useful for generating reports, conducting audits, or sharing processing activity information with stakeholders in their preferred format and language. Note that at least one export format and a language must be specified for a successful request. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `language` | string ("ar" | "de" | "en" | "es" | "es-EC" | "es-MX" | "fr" | "hi" | "it" | "ja" | "pt" | "zh") | Yes | Language | | `exportTypes` | array | Yes | Exporttypes | | `filter__owners` | array | No | Owners | | `filter__search` | string | No | Search | | `filter__status` | array | No | Status | | `filter__employees` | array | No | Employees | | `filter__infotypes` | array | No | Infotypes | | `filter__recipients` | array | No | Recipients | | `filter__departments` | array | No | Departments | | `filter__dataSubjects` | array | No | Datasubjects | | `filter__processingActivityId` | string | No | Processingactivityid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Export recipients list with filter **Slug:** `BORNEO_EXPORT_RECIPIENTS_LIST_WITH_FILTER` The ExportRecipientsList endpoint generates and exports a list of recipients based on specified criteria. It allows for flexible data extraction in multiple formats (CSV, PDF, or DOC) with extensive filtering options. This endpoint is ideal for generating reports, performing data analysis, or creating backups of recipient information. It can handle complex queries to narrow down the recipient list based on various attributes such as categories, roles, processing activities, and more. However, it does not provide real-time updates and should be used for point-in-time exports rather than live data access. The endpoint is particularly useful for compliance reporting, auditing, or transferring recipient data to other systems. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `exportTypes` | array | Yes | Exporttypes | | `filter__role` | array | No | Role | | `filter__search` | string | No | Free-form text search to apply to the Recipient name. | | `filter__status` | string ("archived" | "validated") | No | The status of the recipient. Can be archived or validated. | | `filter__usedIn` | object | No | Usedin | | `filter__categories` | array | No | list of recipient category | | `filter__departments` | array | No | Departments | | `filter__recipientIds` | array | No | Recipientids | | `filter__recipientState` | array | No | Recipientstate | | `filter__discoverySource` | array | No | Discoverysource | | `filter__subProcessorIds` | array | No | Subprocessorids | | `filter__automationStatus` | array | No | Automationstatus | | `filter__recipientWarranties` | array | No | Recipientwarranties | | `filter__withNoProcessingActivity` | boolean | No | Withnoprocessingactivity | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Fetch dashboard report by id **Slug:** `BORNEO_FETCH_DASHBOARD_REPORT_BY_ID` Retrieves a specific dashboard report from the Borneo integration platform. This endpoint allows users to access detailed analytics and reporting data for a particular dashboard, providing insights into data exchange, workflow automation, and potentially sensitive data breach information. It should be used when a user needs to view or analyze a specific report's contents, such as performance metrics, data sharing statistics, or privacy incident details. The endpoint is particularly useful for generating up-to-date reports for monitoring and decision-making purposes. Note that this endpoint only retrieves existing reports and does not generate new ones or modify report data. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dashboardReportId` | string | Yes | Dashboardreportid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Fetch data breach evaluation **Slug:** `BORNEO_FETCH_DATA_BREACH_EVALUATION` Retrieves detailed information about a specific evaluated data breach incident. This endpoint should be used when you need to access comprehensive details about a particular data breach that has been assessed within the Borneo platform. It provides insights into the nature, scope, and potential impact of the breach, which can be crucial for incident response, compliance reporting, and risk assessment. The tool is particularly useful for security teams, compliance officers, and data protection officers who need to review or report on specific data breach incidents. Note that this endpoint only provides information about breaches that have already been evaluated and recorded in the system; it cannot be used to report new breaches or assess ongoing incidents. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dataBreachId` | string | Yes | Identifier of the DataBreach | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Filter and list inspection results **Slug:** `BORNEO_FILTER_AND_LIST_INSPECTION_RESULTS` The InsightListPost endpoint retrieves a list of inspection results from the Borneo integration platform. It allows users to fetch either scan-level or page-level results based on specified criteria. This endpoint is particularly useful for analyzing data security and compliance across various resources and scans. It supports extensive filtering options, pagination for large result sets, and customizable sorting, making it ideal for generating comprehensive reports or conducting detailed investigations into data insights. The endpoint should be used when a detailed overview of inspection results is required, but it may not provide real-time updates for ongoing scans. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `type` | string ("page" | "scan") | Yes | Type of inspection result, i.e. scan-level or page-level results. | | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__pageId` | string | No | Unique page ID. Only applicable to page-level results. | | `filter__scanId` | string | No | Unique scan ID. | | `filter__search` | string | No | Free-text search on the resource name. | | `filter__status` | array | No | Status | | `filter__categories` | array | No | infotype categories | | `filter__userEmails` | array | No | Useremails | | `filter__resourceIds` | array | No | One or more resource IDs for which to retrieve results. Only applicable to page-level results. | | `filter__resourceType` | string | No | Resource type to filter results by. | | `filter__fileExtension` | array | No | Fileextension | | `filter__infoTypes__ops` | string ("AND" | "OR") | No | Ops | | `filter__scanIterationId` | string | No | Unique scan iteration ID to fetch results for a specific run of | | `filter__infotypeConfidence` | array | No | Infotypeconfidence | | `filter__infoTypes__infoTypes` | array | No | The list of infotypes to filter on. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Filter and sort assets list **Slug:** `BORNEO_FILTER_AND_SORT_ASSETS_LIST` The ListAssets endpoint retrieves a customized list of assets from Borneo. It supports flexible filtering and sorting, enabling efficient asset management. Use this endpoint for generating reports, conducting audits, or searching specific items. While powerful, it may not provide detailed asset information in the initial response. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `maxResults` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `filter__type` | array | No | Type | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Free-form text search to apply to the asset name. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Filter employee list **Slug:** `BORNEO_FILTER_EMPLOYEE_LIST` The FilterEmployeeList endpoint allows you to retrieve a filtered list of employees based on specified criteria. This POST operation is designed for querying employee data within the Borneo integration platform, enabling efficient data retrieval for various business processes and integrations. Use this endpoint when you need to fetch a subset of employee records matching particular conditions, such as department, job title, or hire date. The endpoint supports pagination for handling large result sets, making it suitable for applications that need to display or process employee data in manageable chunks. Note that the specific filterable fields may vary depending on your Borneo instance configuration and available employee data. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Filter recipients list **Slug:** `BORNEO_FILTER_RECIPIENTS_LIST` The FilterRecipientsList endpoint allows users to retrieve a filtered list of recipients based on specified criteria. This POST method endpoint is designed to narrow down a potentially large set of recipients to a more manageable subset that meets certain conditions. It's particularly useful for targeting specific groups of recipients for communication, data analysis, or other operations within the Borneo integration platform. The endpoint supports pagination to handle large result sets efficiently. While it provides powerful filtering capabilities, users should be aware that the performance may vary depending on the complexity of the filter criteria and the size of the recipient database. This endpoint should be used when there's a need to identify and work with a specific subset of recipients rather than the entire list. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get category by label **Slug:** `BORNEO_GET_CATEGORY_BY_LABEL` Retrieves detailed information about a specific category within Borneo's data classification system using the category's unique label. This endpoint is used to fetch metadata, attributes, and potentially associated data points for a given category. It's particularly useful for understanding the structure and properties of a category, which can be crucial for data governance, compliance reporting, and workflow automation tasks. The endpoint should be used when detailed information about a specific category is needed, such as during data discovery processes, access governance reviews, or when setting up data lineage mappings. It does not modify any data and is primarily for information retrieval purposes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `categoryLabel` | string | Yes | The name of the infotype category. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get cloud account by id **Slug:** `BORNEO_GET_CLOUD_ACCOUNT_BY_ID` Retrieves detailed information about a specific cloud account within the Borneo integration platform. This endpoint should be used when you need to access or verify the configuration, status, or properties of a particular cloud account. It provides essential data for account management, such as associated services, integration status, and account-specific settings. This tool is particularly useful for administrators managing multiple cloud accounts or for auditing purposes. Note that it only retrieves information and does not modify the account in any way. The endpoint may not provide sensitive information like access keys or full credential details for security reasons. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `cloudAccountId` | string | Yes | The cloud-provider specific account ID, e.g. a 12-digit AWS account ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get dashboard report edition by id **Slug:** `BORNEO_GET_DASHBOARD_REPORT_EDITION_BY_ID` Retrieves a specific edition of a dashboard report from the Borneo integration platform. This endpoint is used to fetch detailed information about a particular version of a report, allowing users to access historical data or compare different iterations of the same report. It's particularly useful for tracking changes in business event impacts over time or analyzing data from specific periods. The endpoint should be used when there's a need to review or analyze a specific report edition, rather than just the most recent data. It may not provide real-time updates and is limited to retrieving one report edition at a time. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `reportEditionId` | string | Yes | Reporteditionid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get department filter list **Slug:** `BORNEO_GET_DEPARTMENT_FILTER_LIST` The FilterDepartmentList endpoint allows users to retrieve a filtered list of departments from the Borneo integration platform. It accepts various filtering criteria to narrow down the results based on department attributes such as name, location, or size. This endpoint is particularly useful for searching specific departments or generating customized department lists for reporting or integration purposes. The filtered results can be sorted and paginated for easier data handling and display. While it provides powerful filtering capabilities, it does not modify any department data and is intended for read-only operations. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get domain by id **Slug:** `BORNEO_GET_DOMAIN_BY_ID` Retrieves detailed information about a specific domain within the Borneo integration platform. This endpoint should be used when you need to access the current configuration, status, or other attributes of a particular domain. It provides a comprehensive view of the domain's settings, which can be useful for auditing, troubleshooting, or gathering information for further operations. The endpoint does not modify any domain data and is safe for frequent use. However, it's important to note that this endpoint only retrieves information for a single domain at a time and does not provide aggregated data across multiple domains. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `domainId` | string | Yes | Identifier of the domain. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get headquarters by id **Slug:** `BORNEO_GET_HEADQUARTERS_BY_ID` Retrieves detailed information about a specific headquarters registered in the Borneo system. This endpoint allows users to access comprehensive data about an organization's headquarters, which may include its location, data governance practices, compliance status, and security measures. It's particularly useful for auditing purposes, reviewing data management strategies, or assessing the overall data security posture of a specific organizational unit. The endpoint should be used when detailed information about a particular headquarters is needed, especially in the context of data security and governance. It may not provide real-time operational data or information about other organizational units not classified as headquarters. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `headquarterId` | string | Yes | The identifier of the headquarter | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get insight by type and id **Slug:** `BORNEO_GET_INSIGHT_BY_TYPE_AND_ID` Retrieves a specific insight from the Borneo platform based on its type and unique identifier. This endpoint is crucial for accessing detailed information about data observability, security, privacy, or compliance issues identified by Borneo's ML-powered classifiers. Use this when you need to fetch comprehensive data about a particular finding, such as sensitive data trends, privacy violations, or security gaps. The endpoint provides focused, in-depth information about a single insight, making it ideal for detailed investigations or generating specific reports. It does not provide aggregated data or lists of multiple insights; for those purposes, you would need to use a different endpoint. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `id` | string | Yes | The unique ID of the inspection result to fetch. | | `type` | string ("page" | "scan") | Yes | The type of inspection result to fetch. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get resource inventory by id **Slug:** `BORNEO_GET_RESOURCE_INVENTORY_BY_ID` Retrieves detailed inventory information for a specific resource identified by its unique resourceId. This endpoint is designed to provide up-to-date data on the quantity, quality, and status of resources managed by Borneo Resource Investments Ltd., such as mineral deposits or gold mines. It should be used when accurate, current inventory data is needed for resource planning, reporting, or analysis purposes. The endpoint returns comprehensive inventory details, which may include resource quantity, grade, extraction status, and other relevant metrics. However, it does not provide historical inventory data or future projections; it only reflects the current state of the resource inventory. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `resourceId` | string | Yes | The unique resource ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get scan by scanid **Slug:** `BORNEO_GET_SCAN_BY_SCAN_ID` Retrieves detailed information about a specific data scan performed by Borneo's data risk remediation platform. This endpoint allows users to fetch the results and metadata of a particular scan, including identified sensitive data, compliance status, and any automated tagging applied. It should be used when you need to review the outcome of a specific scan, track the progress of ongoing scans, or audit historical scan data. The endpoint focuses solely on providing scan-related information and does not modify any data or trigger new scans. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `scanId` | string | Yes | Scanid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get threshold by id **Slug:** `BORNEO_GET_THRESHOLD_BY_ID` Retrieves detailed information about a specific threshold setting in the Borneo integration platform. This endpoint allows users to fetch the configuration and current status of a particular threshold, which may be used for monitoring, alerting, or controlling data flows between integrated systems. It should be used when detailed information about a known threshold is required, such as during system audits, troubleshooting, or when adjusting integration workflows. The endpoint will not modify the threshold settings; it is for retrieval purposes only. Users should ensure they have the correct thresholdId before making the request, as invalid IDs will likely result in error responses. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `thresholdId` | string | Yes | Identifier of the Threshold | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Get user profile by id **Slug:** `BORNEO_GET_USER_PROFILE_BY_ID` Retrieves the user profile information for a specific user in the Borneo integration platform. This endpoint should be used when detailed information about a user's profile is needed, such as for displaying user data, verifying user details, or performing user-related operations within the Borneo ecosystem. The endpoint focuses on providing user-specific data while maintaining Borneo's emphasis on data security and privacy observability. It's important to note that this endpoint only retrieves profile information and does not modify or delete user data. The response will likely include various user attributes, but the exact structure and fields are not specified in the given schema. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `userId` | string | Yes | Userid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List dashboard report editions **Slug:** `BORNEO_LIST_DASHBOARD_REPORT_EDITIONS` Lists the editions of a specific dashboard report in the Borneo integration platform. This endpoint allows users to retrieve a paginated list of dashboard report editions, with options for sorting and specifying the number of results per page. It's particularly useful for managing and reviewing multiple versions or iterations of a dashboard report, enabling users to track changes over time or select specific editions for further analysis or comparison. The endpoint supports efficient navigation through large sets of editions using pagination tokens and customizable sorting, making it suitable for applications that need to display or process dashboard report history. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | Nexttoken | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `dashboardReportId` | string | Yes | The `nextToken` from the last page of results to retrieve the next page of results. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List dashboard reports with filters **Slug:** `BORNEO_LIST_DASHBOARD_REPORTS_WITH_FILTERS` Retrieves a list of dashboard reports from the Borneo integration platform, allowing for filtered, paginated, and sorted results. This endpoint is useful for obtaining an overview of available reports, such as privacy operations dashboards, data discovery dashboards, and privacy ops data flow reports. It supports complex querying through its filter object, enabling users to search by name, type, and frequency. The endpoint facilitates efficient data retrieval through pagination and customizable sorting, making it ideal for applications that need to display or process large sets of report data. Use this when you need to fetch multiple dashboard reports at once, especially when implementing report listing features or performing bulk operations on report data. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `filter__type` | array | No | Type | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Free-form text search to apply to the scan name. | | `filter__frequency` | array | No | Frequency | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List dashboard users with filters **Slug:** `BORNEO_LIST_DASHBOARD_USERS_WITH_FILTERS` Lists and filters dashboard users in the Borneo integration platform based on specified criteria. This endpoint allows retrieval of user data filtered by roles, tenant, organization, and departments. It's useful for user management, access control, and generating reports on user distribution across different organizational units. The endpoint supports complex queries by combining multiple filter criteria, enabling precise user data retrieval for various administrative and analytical purposes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `filter__roles` | array | No | Roles | | `filter__tenantId` | string | No | Tenantid | | `filter__departments` | array | No | Departments | | `filter__organisationId` | integer | No | Organisationid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List data breaches with filters **Slug:** `BORNEO_LIST_DATA_BREACHES_WITH_FILTERS` The ListDataBreaches endpoint retrieves a list of data breaches based on specified filter conditions, allowing for detailed searching and sorting of breach information. It supports pagination for handling large result sets and provides flexible filtering options including free-text search, authority notification status, owner, and breach status. This endpoint is particularly useful for compliance teams, security analysts, and IT administrators who need to monitor, review, or report on data breach incidents within their organization. The tool facilitates efficient data breach management, enabling users to quickly locate specific incidents or generate comprehensive reports based on various criteria. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__owner` | array | No | Owner | | `filter__search` | string | No | Free-form text search to apply to data breaches short description. | | `filter__status` | array | No | Status | | `filter__authoritiesNotified` | array | No | Authoritiesnotified | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List data breach filters **Slug:** `BORNEO_LIST_DATA_BREACH_FILTERS` Retrieves a list of available filter options for data breaches in the Borneo platform. This endpoint allows users to obtain specific filter criteria based on either the owner of the data breach or its current status. It's particularly useful for preparing dynamic filter options in user interfaces or for understanding the range of possible values when filtering data breaches. The endpoint should be called when setting up data breach management dashboards or when implementing search and filter functionality for data breach records. Note that this endpoint only provides filter options and does not return actual data breach information. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `filterType` | string ("owner" | "status") | Yes | Filtertype | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List departments with sort and pagination **Slug:** `BORNEO_LIST_DEPARTMENTS_WITH_SORT_AND_PAGINATION` The ListDepartments endpoint retrieves a list of departments within the Borneo integration platform. It offers flexible querying with filtering, pagination, and sorting options. Use this endpoint to explore organizational structure, manage department hierarchies, or integrate department information into other systems. Note that it does not support creating, updating, or deleting departments. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Free-form text search to apply to the department name. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List discovered document **Slug:** `BORNEO_LIST_DISCOVERED_DOCUMENT` Retrieves a list of discovered documents in the Borneo integration platform, allowing for flexible querying, filtering, and sorting of results. This endpoint is used to fetch information about documents that have been discovered by the system, such as newly added files, deleted documents, or items with specific statuses. It supports pagination for handling large datasets and provides sorting capabilities to organize the results according to user preferences. Use this endpoint when you need to review, monitor, or analyze the discovered documents within your Borneo integration environment. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Free-form text search to apply to the scan name. | | `filter__status` | string ("ADDED" | "DELETED" | "DOMAIN_DELETED" | "IGNORED" | "NEW") | No | Status | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List discovered infotypes **Slug:** `BORNEO_LIST_DISCOVERED_INFOTYPES` The ListDiscoveredInfoTypes endpoint retrieves discovered info types from Borneo, supporting flexible querying, filtering, sorting, and pagination. It's used for exploring sensitive information identified in your data ecosystem, aiding in data governance and compliance monitoring. The endpoint offers advanced filtering and efficient handling of large datasets. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Free-form text search to apply to the scan name. | | `filter__status` | string ("APPROVED" | "APPROVED_AUTOMATICALLY" | "DELETED" | "IGNORED" | "NEW" | "NOT_PRESENT" | "REQUESTED") | No | Status | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List discovered recipients **Slug:** `BORNEO_LIST_DISCOVERED_RECIPIENTS` Lists and retrieves discovered recipients in the Borneo integration platform. This endpoint allows for paginated, sorted, and filtered access to the discovered recipients data. It's designed for efficiently managing and exploring large sets of recipient information, supporting various query parameters for customized result sets. Use this endpoint when you need to browse, search, or analyze discovered recipients based on specific criteria or in a particular order. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Free-form text search to apply to the DiscoveredRecipient name. | | `filter__status` | string ("ignored" | "new") | No | Status of the discovered recipient. Can be new or ignored if it"s marked as ignored. | | `filter__discoverySource` | array | No | Discoverysource | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List domains with pagination and sorting **Slug:** `BORNEO_LIST_DOMAINS_WITH_PAGINATION_AND_SORTING` Retrieves a list of domains in the Borneo integration platform with support for pagination and custom sorting. This endpoint allows users to fetch domain information in manageable chunks and order the results based on specific criteria. It's particularly useful for applications that need to display or process large sets of domain data efficiently. The endpoint does not provide filtering capabilities, so all domains accessible to the authenticated user will be listed. Use this when you need to enumerate or browse through the domains registered in your Borneo account, such as for administrative purposes or to populate domain selection interfaces. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List employees with filters **Slug:** `BORNEO_LIST_EMPLOYEES_WITH_FILTERS` Retrieves a list of employees based on specified filtering and sorting criteria. This endpoint allows for flexible querying of employee data, supporting both simple and complex search scenarios. It can be used to find employees by name, filter by departments, and sort the results based on various attributes. The endpoint is particularly useful for generating reports, populating employee directories, or performing data analysis on the workforce. It does not modify any employee data and is intended for read-only operations. Note that the response structure and pagination details are not specified in the given schema, so additional documentation may be needed for handling large result sets. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Free-form text search to apply to the employee name. | | `filter__department` | array | No | Department | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List error details from filtered scan iterations **Slug:** `BORNEO_LIST_ERROR_DETAILS_FROM_FILTERED_SCAN_ITERATIONS` The ErrorList endpoint retrieves errors related to scan iterations in Borneo. It offers flexible filtering, sorting, and pagination for efficient error analysis. Use for debugging, monitoring, or reporting across various scans and resources. Supports up to 10,000 records per call. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `select` | array | No | List of column names to include in the response. | | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__scanId` | string | No | Scanid | | `filter__accountId` | string | No | Accountid | | `filter__resourceId` | string | No | Resourceid | | `filter__scanExecutionId` | string | No | Scanexecutionid | | `filter__scanIterationId` | string | No | Scaniterationid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List events with filters **Slug:** `BORNEO_LIST_EVENTS_WITH_FILTERS` Lists and retrieves events based on specified criteria, with options for filtering, sorting, and pagination. This endpoint is designed for querying event data in the Borneo integration platform, allowing users to fetch events related to various entities such as issues, resources, scans, and users. It offers flexible querying capabilities through its filter object, custom sorting, and efficient pagination for handling large datasets. Use this endpoint when you need to search, analyze, or monitor events within your Borneo-integrated systems. The endpoint is particularly useful for generating reports, tracking specific issues, or monitoring system activities across different resources and users. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `select` | array | No | Select | | `pageSize` | integer | No | Pagesize | | `nextToken` | string | No | Nexttoken | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__scanId` | array | No | Scanid | | `filter__search` | string | No | Search | | `filter__userId` | array | No | Userid | | `filter__eventId` | array | No | Eventid | | `filter__issueId` | array | No | Issueid | | `filter__issueType` | array | No | Issuetype | | `filter__resourceId` | array | No | Resourceid | | `filter__newInfotypeFound` | boolean | No | Newinfotypefound | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List filtered sorted categories **Slug:** `BORNEO_LIST_FILTERED_SORTED_CATEGORIES` The ListCategories endpoint allows users to retrieve a list of categories from the Borneo integration platform. It provides flexible options for filtering and sorting the results, enabling efficient category management and exploration. This endpoint is particularly useful when you need to fetch a subset of categories or organize them in a specific order for display or processing purposes. The response will include category information based on the applied filters and sorting criteria. Note that this endpoint does not create, update, or delete categories; it is solely for retrieving existing category data. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__categories` | array | No | Categories | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List filter options for recipients **Slug:** `BORNEO_LIST_FILTER_OPTIONS_FOR_RECIPIENTS` Lists the available filters for recipients in the Borneo integration platform based on the specified filter type. This endpoint allows users to retrieve either category-based or role-based filters, which can be used to manage and organize recipients for targeted data distribution or notification purposes. Use this endpoint when you need to access the current set of filters available for recipient management, either by categories or roles. It provides a comprehensive list of filters but does not apply or modify any filters; it's purely for retrieval purposes. This tool is particularly useful for administrators or integrators who need to understand the current filter structure before applying filters to recipients or setting up data distribution rules. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `filterType` | string ("categories" | "role") | Yes | Filtertype | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List headquarters with sorting **Slug:** `BORNEO_LIST_HEADQUARTERS_WITH_SORTING` The headquarters_list endpoint retrieves a paginated list of headquarters records from Borneo. It supports efficient querying of large datasets through pagination and custom sorting. This endpoint is ideal for applications needing to display or process headquarters information in batches, such as for reports or dashboards. It offers flexible result retrieval and sorting capabilities, but lacks built-in filtering options. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List insight filters **Slug:** `BORNEO_LIST_INSIGHT_FILTERS` The list-filters endpoint retrieves a list of available filters for data insights, specifically focused on file extension filters. This tool is used to obtain filtering options for managing and analyzing data within Borneo's integration platform. It's particularly useful when users need to understand or apply filters based on file types in their data streams or integration processes. The endpoint requires a specific scan ID, suggesting that filters are contextual to particular data scans or integration jobs. Currently, the tool is limited to listing file extension filters, which may be used for data categorization, processing, or compliance purposes in data integration workflows. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `scanId` | string | No | Scanid | | `filterType` | string ("fileExtension") | No | Filtertype | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List inventory resources with filters **Slug:** `BORNEO_LIST_INVENTORY_RESOURCES_WITH_FILTERS` Retrieves a comprehensive list of resources from Borneo's inventory. Supports detailed filtering, sorting, and pagination for efficient resource management and analysis across multiple cloud providers. Ideal for security auditing, compliance monitoring, and inventory management tasks. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `select` | array | No | A list of property names to return in the response. If not specified, all resource properties will be returned. | | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | Optional "nextToken" value from the last API response. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__hasPii` | boolean | No | Include only resources that have a high likelihood of containing PII based on the resource metadata. | | `filter__region` | string | No | The region of the cloud account to which the resoure belongs. | | `filter__search` | string | No | Free-text search on the resource name. | | `filter__noOwner` | boolean | No | Include only resources that have not been assigned an owner. | | `filter__regions` | array | No | List of regions to which the resoure belongs to in that cloud account. | | `filter__hasOwner` | boolean | No | Include only resources that have been assigned an owner. | | `filter__parentId` | string | No | The parent Id of the resource. E.g. Borneo-specific GCP subscription ID for GCP resources | | `filter__accountId` | string | No | The account ID of the cloud account to which the resoure belongs. E.g. a 12-digit AWS account ID. | | `filter__dataRisks` | array | No | Filter the resources that has data risks. | | `filter__firstSeen` | object | No | Set of conditions for comparing two timestamps. | | `filter__resourceIds` | array | No | One or more resource IDs to return. | | `filter__resourceTags` | array | No | Filter the resources based on tags | | `filter__resourceType` | string | No | Filter the resources based on the resource type. | | `filter__severityScore` | array | No | Filter the resources based on the assigned risk severity score; "critical" = 4, "high" = 3, "medium" = 2, "low" = 1. | | `filter__classification` | array | No | Filter the resources based on classification and are non-compliant. eg "PII_L1", "PII_L2", "PII_L3". Custom added classifications is also supported. | | `include__violationMetrics` | boolean | No | Include violation count by severity for resource and child resources. | | `filter__hideBorneoResources` | boolean | No | Whether to hide resources that are part of the Borneo data plane. | | `filter__dataSourceCategories` | array | No | Filter the resources based on the data source category Current supported values: AWS_DATA_STORES, GCP_DATA_STORES, STANDALONE_DATA_STORES, CLOUD_APPLICATIONS, DISCOVERED_APPLICATIONS | | `filter__scannableResourceTypes` | boolean | No | Filter the resources that are scannable | | `include__frameworkExceptionsCount` | boolean | No | Include framework exceptions count for the resource and its children | | `include__childResourceStats__scans` | boolean | No | Include aggregate scan stats from child resources. | | `include__childResourceStats__dataSize` | boolean | No | Include aggregate data size stats from child resources. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List issues with filters **Slug:** `BORNEO_LIST_ISSUES_WITH_FILTERS` The ListIssues endpoint allows users to retrieve a filtered and sorted list of issues from the Borneo integration platform. It provides extensive filtering capabilities to narrow down results based on various criteria such as resources, cloud accounts, issue states, and severities. The endpoint supports pagination for handling large result sets efficiently and allows customization of the returned data through column selection and inclusion of related resources. This powerful querying tool is essential for monitoring, troubleshooting, and managing issues across integrated systems and cloud environments in Borneo. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `select` | array | No | List of column names to include in the response. | | `include` | object | No | The set of related resources that should be included in the response using a join-query. | | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Free-text search on the resource name. | | `filter__states` | array | No | List of isssue states to filter by. | | `filter__resources` | array | No | List of resource IDs to filter by. | | `filter__severities` | array | No | List of issue severities to filter by. | | `filter__resourceTypes` | array | No | List of resource types to filter by. | | `filter__failedControls` | array | No | List of failed controls to filter by. | | `filter__cloudAccountIds` | array | No | List of cloud provider account IDs to filter by. | | `filter__cloudAccountTypes` | array | No | List of cloud provider account types to filter by. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List leaf resources with filters **Slug:** `BORNEO_LIST_LEAF_RESOURCES_WITH_FILTERS` The listLeafResources endpoint retrieves and filters leaf resources from Borneo's catalog. It supports detailed searching across various criteria, enabling efficient resource management and discovery. Users can paginate results, include additional information, and sort outputs as needed. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | Optional "nextToken" value from the last API response. | | `sourceType` | string | No | Filter resource based on the resource type. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__region` | array | No | One or more cloud provider regions. | | `filter__schema` | array | No | List tables from a specific schema. Supported for the following resource types: Presto. | | `filter__search` | string | No | Free-text search on the resource name. | | `filter__status` | array | No | Filter the resources based on list of status. | | `filter__account` | array | No | One or more cloud provider account IDs. | | `filter__dataset` | array | No | List tables from a specific dataset. Supported for on the following resource types: BigQuery. | | `filter__driveId` | array | No | List drives from a specific driveId. Supported for the following resource types: Gdrive. | | `filter__noOwner` | boolean | No | Include only resources that have not been assigned an owner. | | `filter__scanned` | boolean | No | Include only resources that have been scanned. | | `filter__database` | array | No | List tables from a specific database. Supported for the following resource types: (RDS) PostgreSQL, (RDS) MySQL, MongoDB. | | `filter__hasOwner` | boolean | No | Include only resources that have been assigned an owner. | | `filter__instance` | array | No | One or more resource IDs of the instances to which the resources belong, i.e. the parent resource ID. | | `filter__parentId` | string | No | Filter the resources which has the specified parent ID. | | `filter__driveType` | array | No | List drives from a specific drive type. Supported for the following resource types: Gdrive. | | `filter__firstSeen` | object | No | Set of conditions for comparing two timestamps. | | `filter__orgUnitId` | array | No | List orgUnits from a specific orgUnitIds. Supported for the following resource types: Gdrive. | | `filter__spaceType` | array | No | Filter conlfluences based on type | | `filter__categories` | array | No | Filter the resources matching with the list of categories. | | `filter__resourceId` | array | No | Filter the resources with the specified resource IDs. | | `filter__spaceStatus` | array | No | Filter conlfluences based on status | | `filter__resourceTags` | array | No | Filter the resources based on tags | | `filter__resourceType` | array | No | Filter the resources which can be scanned by Borneo. | | `filter__severityScore` | array | No | Filter the resources based on the assigned risk severity score; "critical" = 4, "high" = 3, "medium" = 2, "low" = 1. | | `filter__classification` | array | No | Filter the resources matching with the list of classifications. | | `filter__infoTypes__ops` | string ("AND" | "OR") | No | Ops | | `include__violationSummary` | boolean | No | Violationsummary | | `filter__infoTypes__infoTypes` | array | No | The list of infotypes to filter on. | | `include__frameworkExceptionsCount` | boolean | No | Frameworkexceptionscount | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List legal documents with pagination **Slug:** `BORNEO_LIST_LEGAL_DOCUMENTS_WITH_PAGINATION` Retrieves a paginated and sortable list of legal documents based on specified filter criteria. This endpoint allows for efficient searching, filtering, and organizing of legal documents within the Borneo integration platform. It supports free-text search on document names, filtering by document status, and custom sorting options. Use this endpoint when you need to fetch multiple legal documents that match specific criteria or when you want to implement a paginated document browsing feature in your application. The endpoint is particularly useful for document management systems, legal workflow automation, or any scenario requiring bulk retrieval of legal document metadata. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Free-form text search to apply to the scan name. | | `filter__status` | string ("CREATED" | "DELETED" | "SCANNING") | No | Status | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List or filter recipients **Slug:** `BORNEO_LIST_OR_FILTER_RECIPIENTS` The ListRecipients endpoint retrieves a paginated and filtered list of recipients from the Borneo application. It allows for extensive customization of the query through sorting and filtering options, making it suitable for various recipient management and data integration tasks. The endpoint supports pagination for efficient handling of large datasets and provides detailed filtering capabilities to narrow down results based on multiple criteria such as categories, roles, status, and associated entities. This tool is ideal for generating reports, auditing recipient data, or populating user interfaces with recipient information. It should be used when a comprehensive view of recipients is needed, with the ability to apply complex filters and sort the results as required. The endpoint does not modify any data and is solely for retrieval purposes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `filter__role` | array | No | Role | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Free-form text search to apply to the Recipient name. | | `filter__status` | string ("archived" | "validated") | No | The status of the recipient. Can be archived or validated. | | `filter__usedIn` | object | No | Usedin | | `filter__categories` | array | No | list of recipient category | | `filter__departments` | array | No | Departments | | `filter__recipientIds` | array | No | Recipientids | | `filter__recipientState` | array | No | Recipientstate | | `filter__discoverySource` | array | No | Discoverysource | | `filter__subProcessorIds` | array | No | Subprocessorids | | `filter__automationStatus` | array | No | Automationstatus | | `filter__recipientWarranties` | array | No | Recipientwarranties | | `filter__withNoProcessingActivity` | boolean | No | Withnoprocessingactivity | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List processing activities **Slug:** `BORNEO_LIST_PROCESSING_ACTIVITIES` ListProcessingActivities retrieves a list of processing activities with extensive filtering, sorting, and pagination. It's ideal for auditing, reporting, or managing data processing activities. The endpoint supports complex querying via the 'filter' object and efficient pagination. While powerful for retrieval, it doesn't modify records. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__assets` | array | No | Assets | | `filter__owners` | array | No | Owners | | `filter__search` | string | No | Free-form text search to apply to processing activity name. | | `filter__status` | array | No | Status | | `filter__dataTypes` | array | No | Datatypes | | `filter__employees` | array | No | Employees | | `filter__infotypes` | array | No | Infotypes | | `filter__languages` | array | No | Languages | | `filter__recipients` | array | No | Recipients | | `filter__dataSources` | array | No | Datasources | | `filter__departments` | array | No | Departments | | `filter__companyRoles` | array | No | Companyroles | | `filter__dataSubjects` | array | No | Datasubjects | | `filter__paAsDataSource` | array | No | Paasdatasource | | `filter__infotypeCategories` | array | No | Infotypecategories | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List processing activities filters **Slug:** `BORNEO_LIST_PROCESSING_ACTIVITIES_FILTERS` This endpoint retrieves a list of available filters for processing activities in the PoPS (Processing of Personal Data) Dashboard. It allows users to obtain filter options based on various categories related to data processing activities. The endpoint is designed to support dynamic filtering capabilities in the dashboard, enabling users to refine their view of processing activities according to different criteria. Use this endpoint when you need to populate filter options in the user interface or when preparing to filter the main processing activities list. It's important to note that this endpoint only returns the available filter options and does not perform the actual filtering of processing activities. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `filterType` | string ("asset" | "companyRole" | "dataSubject" | "department" | "employee" | "owner" | "recipient" | "status") | Yes | Type of filter to retrieve options for | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List scan execution results **Slug:** `BORNEO_LIST_SCAN_EXECUTION_RESULTS` The ListScanExecutions endpoint retrieves and filters inspection results from scan executions in the Borneo integration platform. It allows users to query scan results with highly granular control, supporting filtering by scan IDs, resource IDs, infotypes, statuses, and confidence levels. This endpoint is particularly useful for analyzing scan outcomes, tracking specific resources, and managing large datasets through pagination and sorting capabilities. It should be used when you need to review or analyze the results of previous scans, especially when dealing with a large number of scanned resources or when looking for specific types of detected information. The endpoint does not perform new scans; it only retrieves and organizes existing scan results. Keep in mind that the response may be truncated if there are more results than the specified page size, requiring the use of the nextToken for subsequent requests to retrieve all relevant data. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | Nexttoken | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__scanId` | string | No | Unique scan ID. | | `filter__search` | string | No | Free-text search on the resource name. | | `filter__statuses` | array | No | Statuses | | `filter__resourceIds` | array | No | One or more resource IDs for which to retrieve results. Only applicable to page-level results. | | `filter__infoTypes__ops` | string ("AND" | "OR") | No | Ops | | `filter__scanIterationId` | string | No | Scaniterationid | | `filter__infotypeConfidence` | array | No | One or more confidence matches for the scan. | | `filter__infoTypes__infoTypes` | array | No | The list of infotypes to filter on. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List scan iterations with filter **Slug:** `BORNEO_LIST_SCAN_ITERATIONS_WITH_FILTER` The ListScanIterations endpoint allows users to retrieve a paginated list of scan iterations with customizable filtering, sorting, and field selection options. This POST request is ideal for querying and analyzing scan iteration data across multiple scans or resources. Use it to fetch specific subsets of scan iterations, sort results based on various criteria, and control the amount of data returned in each API call. The endpoint supports efficient pagination for handling large datasets, making it suitable for both small-scale queries and extensive data analysis tasks. It's particularly useful for monitoring scan progress, auditing scan history, or gathering insights across multiple scan iterations. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `select` | array | No | List of column names to include in the response. | | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__scanId` | string | No | Scanid | | `filter__resourceId` | string | No | Resourceid | | `filter__scanIterationId` | string | No | Scaniterationid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List scans with filters **Slug:** `BORNEO_LIST_SCANS_WITH_FILTERS` The list_scans endpoint retrieves a filtered and sorted list of scans from the Borneo integration platform. It allows users to query scan data with extensive filtering options, including search terms, scan types, connector IDs, resources, data planes, and scan statuses. The endpoint supports pagination for handling large result sets and provides control over the returned fields and sorting order. This tool is particularly useful for monitoring scan activities, analyzing scan results across different resources and connectors, and managing large-scale scanning operations in cloud environments. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `select` | array | No | List of column names to include in the response. | | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Free-form text search to apply to the scan name. | | `filter__status` | array | No | One or more scan statuses (e.g. `inprogress`, `completed`, etc.) to filter results by. | | `filter__scanType` | array | No | One or more scan types (i.e. "full" or "sample") to filter results by. | | `getNextExecution` | boolean | No | IF true, nextExecution will be populated for postponed and repeated scans | | `filter__accountId` | array | No | One or more AWS accounts to filter results by. | | `filter__resources` | array | No | One or more resource IDs to filter results by. | | `filter__connectorId` | array | No | One or more connector IDs to filter results by. | | `filter__dataPlaneId` | array | No | One or more data plane IDs to filter results by. | | `filter__gcpProjectId` | array | No | One or more GCP projects to filter results by. | | `filter__resourceType` | array | No | One or moreresource types to filter results by. | | `filter__dataPlaneName` | array | No | One or more data plane names to filter results by. | | `filter__infoTypes__ops` | string ("AND" | "OR") | No | Ops | | `filter__infoTypes__infoTypes` | array | No | The list of infotypes to filter on. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List toms with filter and pagination options **Slug:** `BORNEO_LIST_TOMS_WITH_FILTER_AND_PAGINATION_OPTIONS` The ListToms endpoint retrieves a filtered, sorted, and paginated list of toms from the Borneo integration platform. It allows for complex querying of tom objects based on various criteria such as text search, categories, types, statuses, and IDs. The endpoint supports pagination for handling large result sets and provides sorting capabilities for customized data presentation. This tool is ideal for browsing, searching, and analyzing collections of toms within the Borneo system, enabling efficient data exploration and management. It should be used when a comprehensive view of toms is needed, subject to specific filtering and sorting requirements. The endpoint does not create, update, or delete toms; it is purely for retrieval and listing purposes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `filter__list` | array | No | List | | `filter__type` | array | No | Type | | `sort__column` | string | No | The column name to sort on. | | `filter__tomId` | array | No | Tomid | | `filter__search` | string | No | Free-form text search to apply to the toms name. | | `filter__status` | array | No | Status | | `filter__category` | array | No | Category | | `filter__objectCategory` | array | No | Objectcategory | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### List user profile with filters and sorting **Slug:** `BORNEO_LIST_USER_PROFILE_WITH_FILTERS_AND_SORTING` The ListUserProfiles endpoint retrieves a paginated and filterable list of user profiles from Borneo. It supports custom querying with search, field selection, sorting, and pagination. Ideal for user management, reporting, and data synchronization tasks. The endpoint offers flexible data retrieval, optimizing for efficiency. Note the 10,000 item limit per request, requiring pagination for larger datasets. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `select` | array | No | Select | | `pageSize` | integer | No | Pagesize | | `nextToken` | string | No | Nexttoken | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Search | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Mark scan false positives by id **Slug:** `BORNEO_MARK_SCAN_FALSE_POSITIVES_BY_ID` Marks specified reports as false positives within a given scan in the Borneo platform. This endpoint is used to refine scan results by identifying and flagging reports that are determined to be false alarms. It helps in improving the accuracy of security scans and reducing noise in the results. The function takes a scan ID and a list of report UUIDs to be marked as false positives. It should be used when security analysts or automated systems have reviewed scan results and identified certain findings as non-issues or false alarms. This action helps in training the system and improving future scan accuracy. Note that this operation is likely irreversible, so care should be taken to ensure only genuinely false positive reports are marked. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `scanId` | string | Yes | The unique scan ID. | | `reports` | array | No | Reports | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Pause scan by id **Slug:** `BORNEO_PAUSE_SCAN_BY_ID` The PauseScan endpoint allows users to temporarily halt an ongoing scan process in the Borneo integration platform. This tool is used to pause the scanning and analysis of sensitive data within connected systems or data streams. It's particularly useful when you need to temporarily suspend data processing for maintenance, to manage system resources, or to address any issues that may have arisen during the scan. The endpoint should be used when there's a need to interrupt a scan without completely terminating it, allowing for later resumption. It's important to note that this action doesn't delete or reset the scan progress; it simply suspends further processing until explicitly resumed. The pause operation is immediate, but any in-progress data processing may complete before the pause takes full effect. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `scanId` | string | Yes | The unique scan ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Poll domain by id **Slug:** `BORNEO_POLL_DOMAIN_BY_ID` This endpoint allows you to initiate a poll operation or submit data for a specific domain within the Borneo integration platform. It is used when you need to gather information, trigger a data collection process, or update the status of a particular domain identified by its unique domainId. The POST method suggests that you're sending data to the server, possibly to start a new poll, update an existing one, or submit responses to a poll. This endpoint should be used when interacting with domain-specific polling functionality in Borneo, such as collecting integration status updates or triggering scheduled data synchronizations. It's important to note that the exact behavior and data requirements may vary depending on the specific implementation and purpose of polling in your Borneo setup. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `domainId` | string | Yes | Identifier of the domain. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post accounts with filter and sort options **Slug:** `BORNEO_POST_ACCOUNTS_WITH_FILTER_AND_SORT_OPTIONS` The ListAccounts endpoint retrieves a filtered and sorted list of accounts from the Borneo platform. It supports complex querying based on various criteria, offers pagination for large datasets, and allows custom sorting. While providing extensive filtering, it doesn't return detailed account information or support real-time updates. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | Optional "nextToken" value from the last API response. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `filter__type` | string | No | Filter accounts by account type. | | `sort__column` | string | No | The column name to sort on. | | `filter__search` | string | No | Search for accounts by name. | | `filter__status` | array | No | Filter accounts by status. | | `filter__accountId` | array | No | Filter accounts by the Borneo account ID. | | `filter__activeStates` | boolean | No | Filters out accounts which are not in deleting or deleted states | | `filter__cloudAccountId` | array | No | Filter accounts by the cloud-provider specific account ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post classification stats **Slug:** `BORNEO_POST_CLASSIFICATION_STATS` Retrieves statistical information about resource classifications based on the specified filter criteria. This endpoint allows you to query classification data for resources in the Borneo integration platform. Use this when you need to analyze the distribution or frequency of specific classifications within your integrated data. The endpoint returns aggregated statistics, not individual resource details. It's particularly useful for generating reports, monitoring classification trends, or validating the effectiveness of your classification processes within Borneo. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `filter__classification` | string | No | Classification | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post connector with filtering options **Slug:** `BORNEO_POST_CONNECTOR_WITH_FILTERING_OPTIONS` Retrieves a filtered and sorted list of connectors from the Borneo integration platform. This endpoint allows you to search, filter, and paginate through available connectors based on various criteria such as names, states, types, and associated resources. It's particularly useful for managing large numbers of connectors, monitoring their states, or finding specific connectors within your integration ecosystem. The endpoint supports advanced filtering options, pagination for handling large result sets, and customizable sorting to organize the returned data. Use this when you need to audit your connector inventory, check the status of multiple connectors, or find connectors matching specific criteria. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | Optional "nextToken" value from the last API response. | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | | `filter__names` | array | No | Filter based on connector name. | | `filter__search` | string | No | Search for connectors by name. | | `filter__states` | array | No | Filter based on connector state. | | `filter__resourceIds` | array | No | Filter based on the resource ID of the data source instance associated with the connector. | | `filter__activeStates` | boolean | No | Filters out connectors which are not in destroying or destroyed states | | `filter__connectorIds` | array | No | Filter based on the connector IDs. | | `filter__dataPlaneIds` | array | No | Filter based on the data plane in which the connector is deployed. | | `filter__resourceTypes` | array | No | Filter based on the resource type that the connector supports. | | `filter__connectorTypes` | array | No | Filter based on the connector type. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post current dashboard user **Slug:** `BORNEO_POST_CURRENT_DASHBOARD_USER` Retrieves or updates information about the currently authenticated user in the Borneo dashboard. This endpoint is designed to provide or modify user-specific data within the context of the Borneo integration platform's dashboard. It should be used when the application needs to access or update the current user's profile, preferences, or permissions. The endpoint relies on the existing authentication context to identify the user, eliminating the need for additional parameters. It's important to note that this endpoint may not provide general user management functions and is specifically tailored for the authenticated user's dashboard experience. #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post dashboard report **Slug:** `BORNEO_POST_DASHBOARD_REPORT` Creates or schedules a dashboard report in the Borneo integration platform for privacy operations and data discovery. This endpoint allows users to generate various types of reports, including Privacy Ops Dashboard, Data Discovery Dashboard, and Privacy Ops Data Flow. It supports both immediate and scheduled report generation with flexible frequency options. The tool is designed to help organizations track sensitive data, ensure compliance, and manage privacy across their infrastructure. Use this endpoint when you need to set up regular privacy and data discovery reports or generate one-time reports for immediate analysis. Note that the endpoint does not provide real-time data but rather creates reports based on the most recent data available at the time of report generation. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | Name | | `roles` | array | No | Roles | | `status` | string ("DELETED" | "ONCE" | "SCHEDULED") | Yes | Status | | `createdBy` | string | No | Createdby | | `frequency` | string ("*/30 * * * *" | "0 */1 * * *" | "0 */12 * * *" | "0 */4 * * *" | "0 */6 * * *" | "0 */8 * * *" | "0 0 * * *" | "0 0 * * 0" | "0 0 1 * *" | "0 0 1 1,4,7,10 *" | "0 0 1 1,7 *") | No | The cron schedule expression to use for a recurring scan. Only a fixed set of cron expressions can be used to run scans at 30 minute, 1 hour, 1 day, or 1 week intervals. | | `reportTypes` | array | Yes | Reporttypes | | `externalEmail` | array | No | Externalemail | | `recipientsEmail` | array | No | Recipientsemail | | `triggerImmediately` | boolean | Yes | Triggerimmediately | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post data breach information **Slug:** `BORNEO_POST_DATA_BREACH_INFORMATION` Creates a new data breach report in the Borneo platform. This endpoint allows users to submit comprehensive information about a data breach incident, including details about the occurrence, discovery, affected data and individuals, security measures, and follow-up actions. The report can be saved as a draft or submitted as a final version. It supports multiple languages and allows for the inclusion of additional related information through UUIDs. This tool should be used when documenting and reporting data breach incidents within an organization, helping to ensure compliance with data protection regulations and facilitating incident response and analysis. It's particularly useful for security teams, compliance officers, and data protection officers who need to maintain detailed records of data breaches. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `language` | string ("ar" | "de" | "en" | "es" | "es-EC" | "es-MX" | "fr" | "hi" | "it" | "ja" | "pt" | "zh") | No | Language | | `createdAt` | integer | No | Createdat | | `createdBy` | string | No | Createdby | | `kindOfData` | string | No | Kindofdata | | `occurredAt` | integer | No | Occurredat | | `description` | string | No | Description | | `saveAsDraft` | boolean | Yes | Saveasdraft | | `consequences` | string | No | Consequences | | `discoveredAt` | integer | No | Discoveredat | | `howDiscovered` | string | No | Howdiscovered | | `peopleInformed` | string | No | Peopleinformed | | `wasIntentional` | string | No | Wasintentional | | `shortDescription` | string | Yes | Shortdescription | | `measuresToPrevent` | string | No | Measurestoprevent | | `affectedPeopleFrom` | string | No | Affectedpeoplefrom | | `authoritiesInformed` | string | No | Authoritiesinformed | | `numberAffectedPeople` | integer | No | Numberaffectedpeople | | `additionalInformation` | array | No | Additionalinformation | | `profilePeopleAffected` | string | No | Profilepeopleaffected | | `compromisedSensitiveData` | string | No | Compromisedsensitivedata | | `problemOfSecurityMeasures` | string | No | Problemofsecuritymeasures | | `securityMeasuresOrProtocols` | string | No | Securitymeasuresorprotocols | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post discovered recipient by id **Slug:** `BORNEO_POST_DISCOVERED_RECIPIENT_BY_ID` Updates or processes information for a specific discovered recipient user in the Borneo integration platform. This endpoint allows you to interact with user data that has been automatically discovered by the system, potentially as part of the integration process between different applications. Use this when you need to modify, confirm, or take action on a discovered user's information. The exact actions performed depend on the request body (not specified in the schema) but may include tasks such as confirming the user's identity, updating their details, or initiating further integration steps. This endpoint is specific to individual users and requires the unique discoveredRecipientId to target the correct record. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `discoveredRecipientId` | string | Yes | Discoveredrecipientid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post filtered access logs **Slug:** `BORNEO_POST_FILTERED_ACCESS_LOGS` The ListAccessLogs endpoint retrieves and filters access logs from the Borneo integration platform. It allows users to search, filter, and paginate through logs based on various criteria such as user email, operation type, request ID, and time range. This endpoint is essential for monitoring system activity, troubleshooting issues, and maintaining security compliance. Use this endpoint when you need to analyze system usage, track specific user actions, or investigate particular requests or operations. It's particularly useful for auditing purposes, performance monitoring, and identifying patterns or anomalies in system access. The endpoint supports detailed filtering options, allowing for precise log retrieval. However, it's important to note that the results are limited to API logs only, and the maximum number of logs returned per call is capped at 10,000. For comprehensive log analysis, multiple calls may be necessary using the pagination feature. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of logs to return per API call. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `filter__end` | string | No | List logs ending in between a specific timestamps with nonoseconds eg. 1715076399359944184. | | `filter__email` | string | No | Filters all logs with user email eg. "user@example.com". | | `filter__start` | string | No | List logs starting in between a specific timestamps with nonoseconds eg. 1715076388657800827. | | `filter__search` | string | No | Free-text search on the logs. | | `filter__requestId` | string | No | List logs from a specific requestId eg. "clvuywyoq009407rj61sxcrpc" | | `filter__operationName` | string | No | List logs based on operation type eg. "ListConnectors", "CreateOktaConnection". | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post log audit records with filter criteria **Slug:** `BORNEO_POST_LOG_AUDIT_RECORDS_WITH_FILTER_CRITERIA` The RetrieveAuditLogs endpoint fetches filtered audit logs from Borneo. It offers extensive filtering options for precise log retrieval across various cloud platforms and system components. Use it for investigations, troubleshooting, and compliance checks. Supports pagination with a 10,000 entry limit per call. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of logs to return per API call. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `filter__end` | string | No | List logs ending in between a specific timestamps with nonoseconds eg. 1715076399359944184. | | `filter__start` | string | No | List logs starting in between a specific timestamps with nonoseconds eg. 1715076388657800827. | | `filter__scanId` | string | No | List logs for a specific scan | | `filter__search` | string | No | Free-text search on the logs. | | `filter__category` | string ("cloudAWS" | "cloudAzure" | "cloudGCP" | "connector" | "dataPlane" | "notification" | "scan") | No | Category | | `filter__accountId` | string | No | List logs for a specific AWS account | | `filter__connectorId` | string | No | List logs for a specific connector | | `filter__dataPlaneId` | string | No | List logs for a specific dataPlane | | `filter__gcpProjectId` | string | No | List logs for a specific GCP project | | `filter__gcpConnectionId` | string | No | List logs for a specific GCP connection | | `filter__azureConnectionId` | string | No | List logs for a specific Azure connection | | `filter__azureSubscriptionId` | string | No | List logs for a specific Azure project | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post resource lineage filter **Slug:** `BORNEO_POST_RESOURCE_LINEAGE_FILTER` Retrieves the lineage information for a specified resource within the Borneo integration platform. This endpoint allows users to trace the data flow both upstream and downstream from a given resource, providing crucial insights into data provenance and impact analysis. It's particularly useful for data governance, compliance tracking, and understanding data transformations within your integrated systems. The endpoint requires specifying the resource ID and the depth of lineage to explore in both directions, enabling fine-grained control over the scope of the lineage query. Use this when you need to understand the origin, transformations, and downstream effects of your data resources in Borneo. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `filter__resourceId` | string | No | Resourceid | | `filter__upstreamDepth` | integer | No | Upstreamdepth | | `filter__downstreamDepth` | integer | No | Downstreamdepth | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post resource stats with deleted resources **Slug:** `BORNEO_POST_RESOURCE_STATS_WITH_DELETED_RESOURCES` Retrieves statistics about resources within the Borneo integration platform. This endpoint provides valuable insights into the current state and usage of resources in your Borneo environment. It can be used to monitor resource utilization, track changes over time, and inform decision-making about resource management and scaling. The endpoint allows for optional inclusion of deleted resources in the statistics, providing flexibility in data analysis. It's particularly useful for administrators and developers who need to understand the overall resource landscape of their Borneo implementation. Note that this endpoint focuses on aggregated statistics and may not provide detailed information about individual resources. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `includeDeletedResources` | boolean | No | Includedeletedresources | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post scan resource status **Slug:** `BORNEO_POST_SCAN_RESOURCE_STATUS` Retrieves and filters the resource status for a specific scan iteration in the Borneo integration platform. This endpoint allows users to fetch detailed information about the status of resources associated with a particular scan, supporting pagination for large datasets and filtering by resource name. It's particularly useful for monitoring the progress of scans, troubleshooting issues with specific resources, or gathering data for reporting purposes. The endpoint should be used when detailed status information about scan resources is required, especially when dealing with large-scale scans that may involve numerous resources. Note that while it supports retrieving up to 10,000 records per call, for very large scans, multiple calls using the nextToken may be necessary to retrieve all data. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `scanId` | string | Yes | The unique scan ID. | | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `filter__name` | string | No | Name | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Post support chat query **Slug:** `BORNEO_POST_SUPPORT_CHAT_QUERY` The POST /support/chat endpoint handles chat support interactions in Borneo. It processes user queries for real-time assistance with platform issues or inquiries. Use this endpoint to start or continue support conversations, enabling interactive problem-solving within Borneo's ecosystem. Not suitable for non-support communications or large data submissions. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `query` | string | Yes | Query | | `sessionId` | string | No | Sessionid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Put tom status and note **Slug:** `BORNEO_PUT_TOM_STATUS_AND_NOTE` Updates a specific Technical Operating Model (TOM) in the Borneo integration platform. This endpoint allows users to modify the implementation status of a TOM, add explanatory notes, and attach relevant documentation. It's primarily used for tracking and managing the lifecycle of TOMs within an organization's integration processes. The endpoint is particularly useful when the status of a TOM changes, when additional context needs to be provided, or when supporting documents need to be linked to the TOM. It should be used to keep TOM information up-to-date and to maintain a clear record of TOM progress and associated documentation. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `note` | string | No | Note | | `tomId` | string | Yes | Tomid | | `status` | string ("available" | "implemented" | "pendingToImplement") | Yes | Status of the TOM, i.e. whether the TOM is already implemented, implementation is pending, or the TOM is not implemented. | | `documentFiles` | array | No | Uploaded file id list. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Remove dashboard user by username **Slug:** `BORNEO_REMOVE_DASHBOARD_USER_BY_USERNAME` Removes a specified user from the dashboard in the Borneo integration platform. This endpoint should be used when you need to revoke a user's access to the dashboard, typically during offboarding processes or when adjusting user permissions. The operation is irreversible, so use it with caution. It only removes the user from the dashboard and does not affect their overall account status in the Borneo platform. This endpoint is particularly useful for administrators managing user access to specific dashboards within the system. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `username` | string | Yes | Username | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Reset dashboard user password **Slug:** `BORNEO_RESET_DASHBOARD_USER_PASSWORD` Initiates a password reset process for a specified dashboard user in the Borneo platform. This endpoint should be used when a user has forgotten their password or needs to change it for security reasons. It triggers the password reset mechanism, which typically involves sending a reset link or temporary password to the user's registered email address. This tool does not actually change the password but starts the secure reset process. It's important to note that this endpoint doesn't return the new password or reset token directly for security reasons. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `username` | string | Yes | Username | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Resume scan by id **Slug:** `BORNEO_RESUME_SCAN_BY_ID` The ResumeDataScan endpoint allows users to resume a previously paused or interrupted data scan operation within the Borneo integration platform. This PUT request is used to continue the scanning process for privacy risks or data vulnerabilities that was halted earlier. The endpoint is particularly useful in scenarios where a scan was temporarily stopped due to system maintenance, network issues, or intentional pausing. It should be used when there's a need to complete an unfinished scan without starting the entire process from the beginning. This tool doesn't initiate new scans or modify the scan parameters; it simply continues the existing scan from where it left off. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `scanId` | string | Yes | The unique scan ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve account details by id **Slug:** `BORNEO_RETRIEVE_ACCOUNT_DETAILS_BY_ID` Retrieves detailed information for a specific account within the Borneo integration platform. This endpoint should be used when you need to access comprehensive account data, including settings, permissions, integration configurations, and other relevant information associated with the account. It's particularly useful for account management tasks, auditing, or when displaying account details in a user interface. The endpoint returns the most up-to-date information available for the specified account. Note that this endpoint does not provide real-time data security or privacy observability information; for those features, you may need to use separate dedicated endpoints within the Borneo API. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `accountId` | string | Yes | The unique Borneo account ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve asset by id **Slug:** `BORNEO_RETRIEVE_ASSET_BY_ID` Retrieves detailed information about a specific asset within the Borneo integration platform. This endpoint allows users to fetch comprehensive data about a single asset, including its properties, metadata, and current status. It should be used when detailed information about a particular asset is needed, such as during asset management, auditing, or when integrating asset data with other systems. The endpoint provides a snapshot of the asset's current state and attributes, which can be crucial for decision-making in data governance, security analysis, or integration processes. Note that this endpoint only retrieves information and does not modify the asset in any way. It may not provide historical data or version history of the asset, focusing instead on its current state. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `assetId` | string | Yes | Identifier of the asset | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve connector by id **Slug:** `BORNEO_RETRIEVE_CONNECTOR_BY_ID` Retrieves detailed information about a specific connector in the Borneo integration platform. This endpoint allows you to fetch the configuration, status, and other relevant details of a connector using its unique identifier. Use this endpoint when you need to inspect or troubleshoot a particular connector's settings or performance. It's particularly useful for administrators or developers managing integrations within the Borneo ecosystem. The endpoint will not modify any connector settings; it's a read-only operation designed for information retrieval only. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `connectorId` | string | Yes | The unique Borneo connector ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve data breach by id **Slug:** `BORNEO_RETRIEVE_DATA_BREACH_BY_ID` Retrieves detailed information about a specific data breach incident using its unique identifier. This endpoint is crucial for investigating and managing data breaches within the Borneo platform. It provides comprehensive details about the breach, which may include the date of occurrence, affected data types, potential impact, and current status of the breach. Use this endpoint when you need in-depth information about a particular data breach for compliance reporting, incident response, or forensic analysis. The endpoint focuses solely on providing information and does not perform any actions or modifications related to the data breach. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dataBreachId` | string | Yes | Identifier of the DataBreach | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve data resource statistics **Slug:** `BORNEO_RETRIEVE_DATA_RESOURCE_STATISTICS` Retrieves comprehensive statistical information about data resources across the Borneo integration platform. This endpoint provides valuable insights into the overall data landscape, including metrics related to data security, privacy intelligence, and observability. It should be used when you need a high-level overview of your data resources, including potential security risks, privacy compliance status, and data distribution across integrated systems. The endpoint does not accept any parameters, suggesting it returns a complete snapshot of data stats for all accessible resources. Keep in mind that the response may be extensive and could take longer to process for large-scale integrations with numerous data sources. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `sourceType` | string | No | Sourcetype | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve department information **Slug:** `BORNEO_RETRIEVE_DEPARTMENT_INFORMATION` Retrieves detailed information about a specific department within the Borneo integration platform. This endpoint is part of the DepartmentsAPI and is used to fetch comprehensive data about a single department, including its configuration, associated workflows, and integration settings. It's particularly useful when you need to review or audit a department's setup within the Borneo ecosystem. The endpoint should be used when detailed information about a specific department is required, such as during troubleshooting, reporting, or when updating department configurations. Note that this endpoint only provides read access to department data and cannot be used to modify department information. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `departmentId` | string | Yes | Identifier of the department. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve discovered document by id **Slug:** `BORNEO_RETRIEVE_DISCOVERED_DOCUMENT_BY_ID` Retrieves detailed information about a specific discovered document within the Borneo system. This endpoint allows users to access metadata, content, or processing status of a document that has been ingested, processed, or otherwise managed by Borneo's document management capabilities. It should be used when detailed information about a particular document is needed, such as during workflow processing, auditing, or information retrieval tasks. The endpoint is particularly useful for tracking the lifecycle of a document within Borneo's ecosystem, from discovery to final processing or archival stages. Note that this endpoint only provides information about a single document; for bulk operations or document listings, a different endpoint would be more appropriate. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `discoveredDocumentId` | string | Yes | Discovereddocumentid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve discovered infotype by id **Slug:** `BORNEO_RETRIEVE_DISCOVERED_INFOTYPE_BY_ID` Retrieves detailed information about a specific discovered infotype from the Borneo platform. This endpoint is used to access the characteristics, classification, and metadata of a particular data type that has been identified and categorized during the data discovery process. It is particularly useful for understanding the nature of sensitive or important data within your organization's systems. The endpoint should be used when you need to review or analyze the properties of a specific discovered infotype, such as its sensitivity level, applicable compliance rules, or prevalence in your data landscape. It does not modify or create new infotypes; it only provides read access to existing discovered infotype information. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `discoveredInfotypeId` | string | Yes | Discoveredinfotypeid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve discovered recipient by id **Slug:** `BORNEO_RETRIEVE_DISCOVERED_RECIPIENT_BY_ID` Retrieves detailed information about a specific discovered recipient using their unique identifier. This endpoint is part of the recipient management and discovery process within the Borneo integration platform. It should be used when you need to access comprehensive data about a particular recipient that has been identified or discovered by the system. The endpoint is useful for verifying recipient details, updating records, or integrating recipient information into other workflows. Note that this endpoint only provides information for recipients that have already been discovered and added to the system; it cannot be used to search for new recipients or modify existing recipient data. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `discoveredRecipientId` | string | Yes | Identifier of the discovered recipient. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve dpia by id **Slug:** `BORNEO_RETRIEVE_DPIA_BY_ID` Retrieves a specific Data Protection Impact Assessment (DPIA) using its unique identifier. This endpoint is used to access detailed information about a particular DPIA, which is crucial for understanding and managing privacy risks associated with data processing activities in Borneo's conservation and resource management efforts. It should be used when detailed information about a specific DPIA is required, such as for reviewing, updating, or referencing the assessment. The endpoint does not provide a list of all DPIAs or create new ones; it is specifically for retrieving individual DPIA records. Users should ensure they have the correct DPIA identifier before making the request, as incorrect identifiers will likely result in a "not found" error. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dpiaId` | string | Yes | Identifier of the DPIA | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve employee details by id **Slug:** `BORNEO_RETRIEVE_EMPLOYEE_DETAILS_BY_ID` Retrieves detailed information for a specific employee within the Borneo integration platform. This endpoint should be used when you need to access comprehensive data about an individual employee, such as their personal details, job information, or any other relevant data stored in the system. It's particularly useful for displaying employee profiles, verifying employee information, or as part of more complex workflows that require up-to-date employee data. The endpoint returns a single employee record based on the provided employee ID. Note that this endpoint only retrieves data and does not modify any employee information. It should not be used for bulk data retrieval or when you need summarized information about multiple employees. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `employeeId` | string | Yes | Identifier of the employee | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve error details by id **Slug:** `BORNEO_RETRIEVE_ERROR_DETAILS_BY_ID` The GetErrorDetails endpoint retrieves detailed information about a specific error in the Borneo integration platform using its unique identifier. This tool is designed to provide comprehensive error data, including error type, description, timestamp, and any associated metadata, which is crucial for effective error management and resolution. It should be used when investigating specific error occurrences, troubleshooting issues, or gathering data for error analysis and reporting. The endpoint is particularly useful for system administrators, developers, and support teams who need to access detailed error information quickly. However, it does not provide aggregated error statistics or perform any error resolution actions; it's purely for fetching individual error details. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `errorId` | string | Yes | The unique resource ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve issue by id **Slug:** `BORNEO_RETRIEVE_ISSUE_BY_ID` Retrieves detailed information about a specific issue in the Borneo system. This endpoint should be used when you need to fetch comprehensive data about a particular issue, such as its current status, associated tasks, or related workflow information. It's particularly useful for tracking the progress of data integration processes, workflow automation tasks, or privacy compliance issues. The endpoint returns a single issue's details and does not provide a list or summary of multiple issues. Note that the exact structure of the returned data is not specified in the given schema, so users should be prepared to handle various fields related to issue management in Borneo's context. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `issueId` | string | Yes | The unique issue ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve legal document by id **Slug:** `BORNEO_RETRIEVE_LEGAL_DOCUMENT_BY_ID` Retrieves a specific legal document from the Borneo system using its unique identifier. This endpoint is designed to access individual legal documents related to Borneo, such as the Native Courts Ordinance, the Malaysia Agreement, or other important legal frameworks and governance documents. It should be used when detailed information about a particular legal document is required. The endpoint returns the full content and metadata of the requested document. It does not provide search functionality or return multiple documents; for those purposes, a separate endpoint would be necessary. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `documentId` | string | Yes | Documentid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve lopdp threshold by id **Slug:** `BORNEO_RETRIEVE_LOPDP_THRESHOLD_BY_ID` Retrieves detailed information about a specific LOPDP (Logical Object Data Point) threshold configuration within the Borneo integration platform. This endpoint is used to access the settings and parameters of a particular threshold, which are crucial for monitoring system performance and triggering alerts. It should be used when detailed information about a specific threshold's configuration is needed, such as during system audits, troubleshooting, or when adjusting monitoring parameters. The endpoint does not modify any settings; it only provides read access to the existing configuration. Keep in mind that the response will likely include sensitive system configuration data, so access should be restricted to authorized personnel. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `lopdpThresholdId` | string | Yes | Identifier of the Threshold | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve processing activity by id **Slug:** `BORNEO_RETRIEVE_PROCESSING_ACTIVITY_BY_ID` Retrieves detailed information about a specific processing activity within the Borneo platform. This endpoint allows users to access comprehensive data related to a particular data processing task or workflow, including its current status, associated metadata, and any relevant compliance information. It is particularly useful for monitoring ongoing activities, auditing past processes, or gathering information for reporting purposes. The endpoint should be used when detailed insights into a single processing activity are required, but it won't provide an overview of multiple activities or system-wide statistics. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `processingActivityId` | string | Yes | Identifier of the Processing Activity | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve recipient details **Slug:** `BORNEO_RETRIEVE_RECIPIENT_DETAILS` Retrieves detailed information about a specific recipient identified by their unique recipientId within the Borneo integration platform. This endpoint is used to fetch comprehensive data about a recipient, which may include personal details, contact information, associated accounts, or any other relevant data stored in the Borneo system. It's particularly useful when you need to access or display a recipient's full profile or verify their information. The endpoint should be used when detailed recipient information is required for operations such as data verification, profile updates, or displaying recipient details in a user interface. Note that this endpoint only provides read access to recipient data and cannot be used to modify recipient information. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `recipientId` | string | Yes | Identifier of the Recipient | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve recipient processing activities **Slug:** `BORNEO_RETRIEVE_RECIPIENT_PROCESSING_ACTIVITIES` Retrieves a paginated list of processing activities associated with a specific recipient in the Borneo integration platform. This endpoint allows you to fetch and navigate through large sets of processing activity data efficiently. It supports sorting and pagination to help manage the volume of data returned. Use this endpoint when you need to review or analyze the processing activities for a particular recipient, such as for compliance audits or data governance purposes. The endpoint does not provide filtering capabilities beyond the recipient ID, so all processing activities for the specified recipient will be included in the results. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageSize` | integer | No | The maximum number of records to return per API call. If more records are available, the response will be truncated and will contain a "nextToken" value, which can be used to return additional records. | | `nextToken` | string | No | The `nextToken` from the last page of results to retrieve the next page of results. | | `recipientId` | string | Yes | Identifier of the Recipient | | `sort__order` | string ("ASC" | "DESC") | No | Order | | `sort__column` | string | No | The column name to sort on. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve resource catalog by id **Slug:** `BORNEO_RETRIEVE_RESOURCE_CATALOG_BY_ID` Retrieves detailed information about a specific resource from the Borneo catalog using its unique identifier. This endpoint is used to access comprehensive data about a particular resource, which could include metadata, associated files, or other relevant information. It should be used when detailed information about a known resource is required, such as for display purposes or further processing within an integration workflow. The endpoint will not modify the resource or return information about multiple resources. It's important to note that the response structure is not specified in the given schema, so users should refer to Borneo's documentation for the exact format of the returned data. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `resourceId` | string | Yes | The unique resource ID. | | `includeParentDetails` | boolean | No | Includeparentdetails | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve resource columns **Slug:** `BORNEO_RETRIEVE_RESOURCE_COLUMNS` Retrieves column information for resources in the Borneo integration platform. This endpoint allows users to fetch metadata about the structure of resources, including column names, data types, and potentially other attributes. It's particularly useful when you need to understand the schema of available resources for integration purposes or data analysis. The endpoint returns a comprehensive list of columns across all accessible resources, enabling developers to plan data mappings, transformations, or queries effectively. Note that while this endpoint provides structural information, it does not return the actual data contained within the columns. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dataspace` | array | No | Dataspace | | `searchKey` | string | No | Searchkey | | `resourceId` | array | No | Resourceid | | `sourceType` | string | No | Sourcetype | | `parentResourceId` | string | Yes | Parentresourceid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Retrieve tom by id **Slug:** `BORNEO_RETRIEVE_TOM_BY_ID` Retrieves detailed information about a specific Tom resource using its unique identifier. This endpoint is crucial for accessing individual Tom data within the Borneo integration platform. It should be used when you need to fetch comprehensive details about a particular Tom, such as its configuration, status, or associated metadata. The endpoint is particularly useful for monitoring, updating, or troubleshooting specific Tom instances in your integration workflows. Note that this endpoint only provides information for a single Tom and cannot be used to list or search multiple Toms simultaneously. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `tomId` | string | Yes | Identifier of the TOM | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Scan legal document byid **Slug:** `BORNEO_SCAN_LEGAL_DOCUMENT_BY_ID` Initiates a scanning process for a specified legal document within the Borneo integration platform. This endpoint is used to digitize and process a legal document, making it available for further analysis, storage, or integration with other systems. The scan operation is asynchronous, meaning it will start the scanning process but may not immediately return the results. Use this endpoint when you need to convert a physical or digital legal document into a format that can be easily managed and searched within the Borneo ecosystem. It's particularly useful for automating the intake of new legal documents into the system. Note that this endpoint only initiates the scan and does not provide immediate access to the scanned content; additional API calls may be required to retrieve the processed document or check the scan status. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `documentId` | string | Yes | Documentid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Stop scan via scanid **Slug:** `BORNEO_STOP_SCAN_VIA_SCAN_ID` Stops an ongoing scan operation in the Borneo integration platform. This endpoint allows users to halt a specific scan process that is currently in progress. It should be used when there's a need to interrupt a scan before its natural completion, such as when the scan is taking too long, consuming excessive resources, or if the desired information has already been obtained. The endpoint requires the unique identifier of the scan to be stopped, ensuring precise control over individual scan operations. It's important to note that stopping a scan may result in incomplete data collection or analysis, so it should be used judiciously. This operation is irreversible; once stopped, a scan cannot be resumed and would need to be restarted if further scanning is required. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `scanId` | string | Yes | The unique scan ID. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Submit chat feedback **Slug:** `BORNEO_SUBMIT_CHAT_FEEDBACK` The SubmitChatFeedback endpoint allows users to provide feedback on a chat support interaction within the Borneo integration platform. This endpoint is crucial for collecting user satisfaction data, which can be used to improve the quality of support and enhance the overall user experience. It should be called after a chat support session has concluded, enabling users to rate their interaction with the support team. The feedback submitted through this endpoint can help Borneo identify areas for improvement in their support processes and recognize high-performing support agents. Note that this endpoint focuses solely on collecting numerical ratings and does not appear to support additional comments or detailed feedback. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `postId` | string | No | Postid | | `rating` | integer | No | Rating | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Submit detailed scan results **Slug:** `BORNEO_SUBMIT_DETAILED_SCAN_RESULTS` Retrieves detailed insights for a specific scan iteration of a particular resource in the Borneo integration platform. This endpoint allows users to access in-depth information about scan results, which can be used for thorough analysis, troubleshooting, or reporting purposes. It's particularly useful when you need to examine the outcomes of a specific scan iteration in detail, either for the entire scan or for a specific page within the scan results. The endpoint requires both the resource and scan iteration identifiers to ensure precise retrieval of the relevant data. Use this when you need comprehensive information about a scan's findings, especially in scenarios involving data quality assessment, integration verification, or system health checks. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `pageId` | string | No | Page ID for one of the pages produced by the scan. | | `scanId` | string | Yes | Scan ID of the scan that produced the inspection result. | | `resourceId` | string | Yes | Resource ID for the resource for which the page was produced. | | `scanIterationId` | string | Yes | ScanIteration ID of the scan that produced the inspection result. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Trigger dashboard report by report id **Slug:** `BORNEO_TRIGGER_DASHBOARD_REPORT_BY_REPORT_ID` Triggers the generation or retrieval of a specific dashboard report in the Borneo integration platform. This endpoint is used to initiate the process of compiling and presenting data for a predefined dashboard report. It's particularly useful when you need to refresh or generate an up-to-date version of a report on demand. The endpoint should be called when a user or system requires the latest data to be reflected in a dashboard report. It's important to note that this endpoint only initiates the report generation process and may not immediately return the report data. Depending on the complexity and size of the report, there might be a processing time before the actual report becomes available. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dashboardReportId` | string | Yes | Dashboardreportid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update asset information by id **Slug:** `BORNEO_UPDATE_ASSET_INFORMATION_BY_ID` The UpdateAsset endpoint allows you to modify the details of an existing asset in the Borneo integration platform. This PUT operation at `/assets/{assetId}` updates the specified asset's information, including its name, type, associated IDs, and location details. It's crucial for maintaining accurate and up-to-date asset records within the system. Use this endpoint when you need to change any attribute of an asset, such as its name, type, or location. The endpoint requires at least the asset's name and type, with options to update additional properties like associated TOM IDs and location information. Note that this operation will overwrite the existing asset data, so include all required fields even if only updating a subset of properties. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | Name of the asset | | `type` | string ("applications" | "cloudServices" | "communications" | "dataInformation" | "externalStorage" | "filingRoom" | "furniture" | "hardware" | "hosting" | "other" | "paperDocumentation" | "printer" | "server" | "shredder" | "videoSurveillance") | Yes | Indicates the type of the asset. An asset can be one of the several options. | | `tomIds` | array | No | Tomids | | `assetId` | string | Yes | Identifier of the asset | | `locationId` | string | No | Locationid | | `locationType` | string ("external" | "office" | "remote") | No | Locationtype | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update category infotypes **Slug:** `BORNEO_UPDATE_CATEGORY_INFOTYPES` Updates the infotypes associated with a specific category in the Borneo integration platform. This endpoint allows you to modify the list of infotypes belonging to a category and optionally update the category's description. It's used for maintaining and organizing the classification of data types within the system, which is crucial for efficient data exchange and workflow automation. The endpoint replaces the entire list of infotypes for the specified category, so it should be used carefully to ensure no unintended removal of existing infotypes. This operation is particularly useful when restructuring data classifications or when new types of information need to be incorporated into existing categories. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `infotypes` | array | Yes | The list of infotypes that belong to this category. | | `description` | string | No | The description of the infotype category. | | `categoryLabel` | string | Yes | The name of the infotype category. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update dashboard report frequency and recipients **Slug:** `BORNEO_UPDATE_DASHBOARD_REPORT_FREQUENCY_AND_RECIPIENTS` Updates the settings of an existing dashboard report in the Borneo integration platform. This endpoint allows you to modify the recipients, roles, and frequency of a specific dashboard report. Use this when you need to change who receives the report, adjust access permissions, or alter the schedule for report generation. The function is particularly useful for maintaining up-to-date distribution lists and ensuring that reports are generated and sent at the most appropriate intervals for your organization's needs. Note that this endpoint only updates the report settings and does not generate or send the report itself. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `roles` | array | No | Roles | | `frequency` | string ("*/30 * * * *" | "0 */1 * * *" | "0 */12 * * *" | "0 */4 * * *" | "0 */6 * * *" | "0 */8 * * *" | "0 0 * * *" | "0 0 * * 0" | "0 0 1 * *" | "0 0 1 1,4,7,10 *" | "0 0 1 1,7 *") | No | The cron schedule expression to use for a recurring scan. Only a fixed set of cron expressions can be used to run scans at 30 minute, 1 hour, 1 day, or 1 week intervals. | | `externalEmail` | array | No | Externalemail | | `recipientsEmail` | array | No | Recipientsemail | | `dashboardReportId` | string | Yes | Dashboardreportid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update dashboard user details **Slug:** `BORNEO_UPDATE_DASHBOARD_USER_DETAILS` Updates the information of an existing dashboard user in the Borneo integration platform. This endpoint allows you to modify the name associated with a user's account while maintaining their unique username. It should be used when there's a need to update a user's display name or correct any errors in the existing name. The endpoint requires both the username (for identification) and the new name to be provided. It's important to note that this operation only updates the user's name and does not affect any other user data or permissions. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | Name | | `username` | string | Yes | Username | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update dashboard user roles **Slug:** `BORNEO_UPDATE_DASHBOARD_USER_ROLES` Updates the roles and department associations for a specified user across multiple organizations in the Borneo dashboard. This endpoint allows administrators to modify a user's access levels and departmental affiliations within the Borneo system. It's particularly useful for managing user permissions when responsibilities change or when adjusting access across different organizations and departments. The endpoint requires specifying the username and at least one organization with assigned roles. Department associations are optional but must be provided as valid UUIDs when included. This tool should be used when there's a need to modify existing user role configurations, not for creating new users or removing users from the system entirely. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `username` | string | Yes | Username | | `organisations` | array | Yes | Organisations | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update data breach entry **Slug:** `BORNEO_UPDATE_DATA_BREACH_ENTRY` The UpdateDataBreach endpoint allows users to create or update detailed information about a specific data breach incident in the Borneo integration platform. This endpoint is crucial for maintaining accurate and comprehensive records of data breach incidents, which is essential for compliance, risk management, and improving security measures. The endpoint captures a wide range of information about the data breach, including its occurrence, discovery, affected parties, potential consequences, and measures taken in response. It provides flexibility by allowing users to save the information as a draft or finalize the report. This endpoint should be used when there's a need to document a new data breach or update existing information about a breach. It's particularly useful for security teams, compliance officers, and risk management professionals who need to maintain detailed records of security incidents. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `createdBy` | string | No | Createdby | | `kindOfData` | string | No | Kindofdata | | `occurredAt` | integer | No | Occurredat | | `description` | string | No | Description | | `saveAsDraft` | boolean | Yes | Saveasdraft | | `consequences` | string | No | Consequences | | `dataBreachId` | string | Yes | Identifier of the DataBreach | | `discoveredAt` | integer | No | Discoveredat | | `howDiscovered` | string | No | Howdiscovered | | `peopleInformed` | string | No | Peopleinformed | | `wasIntentional` | string | No | Wasintentional | | `shortDescription` | string | Yes | Shortdescription | | `measuresToPrevent` | string | No | Measurestoprevent | | `affectedPeopleFrom` | string | No | Affectedpeoplefrom | | `authoritiesInformed` | string | No | Authoritiesinformed | | `numberAffectedPeople` | integer | No | Numberaffectedpeople | | `additionalInformation` | array | No | Additionalinformation | | `profilePeopleAffected` | string | No | Profilepeopleaffected | | `compromisedSensitiveData` | string | No | Compromisedsensitivedata | | `problemOfSecurityMeasures` | string | No | Problemofsecuritymeasures | | `securityMeasuresOrProtocols` | string | No | Securitymeasuresorprotocols | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update department name **Slug:** `BORNEO_UPDATE_DEPARTMENT_NAME` This endpoint updates the information of an existing department within the Borneo integration platform. It allows you to modify the name of a specific department identified by its unique departmentId. Use this endpoint when you need to rename a department or correct its name in the system. The endpoint is particularly useful for maintaining accurate organizational structure data, which is crucial for workflow automation and integration processes. Note that this operation only updates the department's name and does not affect any other attributes or associations of the department. Ensure that the new name adheres to your organization's naming conventions and accurately represents the department's function. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | No | Name | | `departmentId` | string | Yes | Identifier of the department. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update discovered document status **Slug:** `BORNEO_UPDATE_DISCOVERED_DOCUMENT_STATUS` This endpoint updates the status of a specific discovered document in the Borneo integration platform. It is used as part of the workflow automation process to manage the lifecycle of documents within the system. The endpoint accepts a document ID and a new status, allowing users to change how the document is treated in subsequent processes. This tool should be used when there's a need to modify the processing state of a discovered document, such as marking it for deletion or indicating that it has been successfully added to the system. It's important to note that this endpoint only updates the status and doesn't perform any other operations on the document itself. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `status` | string ("ADDED" | "DELETED" | "DOMAIN_DELETED" | "IGNORED" | "NEW") | Yes | Status | | `discoveredDocumentId` | string | Yes | Discovereddocumentid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update discovered infotype status **Slug:** `BORNEO_UPDATE_DISCOVERED_INFOTYPE_STATUS` Updates the status of a specific discovered infotype in the Borneo integration platform. This endpoint allows users to change the state of an infotype that has been identified during data discovery processes. It is used to manage the lifecycle of discovered infotypes, enabling actions such as approval, ignoring, or deletion. The endpoint should be called when there's a need to change the current status of a discovered infotype, typically as part of data governance or classification workflows. It's important to note that this endpoint only updates the status and doesn't provide additional information about the infotype itself. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `status` | string ("APPROVED" | "APPROVED_AUTOMATICALLY" | "DELETED" | "IGNORED" | "NEW" | "NOT_PRESENT" | "REQUESTED") | Yes | Status | | `discoveredInfotypeId` | string | Yes | Discoveredinfotypeid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update domain details **Slug:** `BORNEO_UPDATE_DOMAIN_DETAILS` Updates the properties of an existing domain within the Borneo integration platform. This endpoint allows you to modify the name and polling frequency of a specific domain identified by its unique domainId. Use this when you need to rename a domain or adjust its automated polling schedule. It's particularly useful for fine-tuning the integration processes or adapting to changing business requirements. The endpoint doesn't provide information about other domain properties or the success of the update operation, so additional verification may be necessary after making changes. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | Name of the domain. | | `domainId` | string | Yes | Identifier of the domain. | | `frequency` | string ("12h" | "1d" | "1w" | "30d" | "6h" | "manual") | Yes | Frequency of polling for a domain. Manual polling means that this domain will not be polled automatically. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update dpia by id **Slug:** `BORNEO_UPDATE_DPIA_BY_ID` Updates an existing Data Protection Impact Assessment (DPIA) in the Borneo system. This endpoint allows for comprehensive modification of a DPIA's privacy framework, risk assessments (confidentiality, integrity, and availability), and associated metadata. It's used to refine and complete a DPIA throughout its lifecycle, from draft to activation. The tool supports detailed documentation of privacy principles, risk analyses, and mitigation measures. It's particularly useful for privacy professionals and data protection officers managing complex data processing activities. Note that activating a DPIA requires filling in numerous mandatory fields, ensuring a thorough privacy impact assessment. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dpiaId` | string | Yes | Identifier of the DPIA | | `status` | string ("activated" | "draft") | Yes | The status of the DPIA. If a DPIA is saved as activated, several fields are required | | `translations` | object | No | Translations | | `integrity__impacts` | array | No | List of impacts that integrity risk can have. At least one element is necessary DPIA is saved as activated | | `integrity__threats` | array | No | List of threats that integrity risk can have. At least one element is necessary DPIA is saved as activated | | `additionalInformation` | string | No | Additionalinformation | | `availability__impacts` | array | No | List of impacts that availability risk can have. At least one element is necessary DPIA is saved as activated | | `availability__threats` | array | No | List of threats that availability risk can have. At least one element is necessary DPIA is saved as activated | | `integrity__plannedToms` | array | No | List of TOMs that are planned to be implemented to prevent integrity risk. At least one element is necessary DPIA is saved as activated | | `integrity__riskSources` | array | No | List of risk sources that integrity risk can have. At least one element is necessary DPIA is saved as activated | | `confidentiality__impacts` | array | No | List of impacts that confidentiality risk can have. At least one element is necessary DPIA is saved as activated | | `confidentiality__threats` | array | No | List of threats that confidentiality risk can have. At least one element is necessary DPIA is saved as activated | | `availability__plannedToms` | array | No | List of TOMs planned to be implemented and that applies to the availability risk. At least one element is necessary DPIA is saved as activated | | `availability__riskSources` | array | No | List of risk sources that availability risk can have. At least one element is necessary DPIA is saved as activated | | `integrity__impactsComment` | string | No | Comment to add additional information about the integrity impacts | | `integrity__threatsComment` | string | No | Comment to add additional information about the integrity threats | | `privacyFramework__consent` | string | No | Field to describe the measures to ensure that the consent of the data subjects has been obtained and how the given consent can be revoked Mandatory if DPIA is saved as activated and the lawfulness "consent_person_concerned" selected | | `additionalInformationFiles` | array | No | Additionalinformationfiles | | `integrity__baselineComment` | string | No | Comment to add additional information about the baseline risk of the integrity | | `integrity__implementedToms` | array | No | List of TOMs that are implemented to prevent integrity risk. At least one element is necessary DPIA is saved as activated | | `privacyFramework__accuracy` | string | No | Field to explain if the data processed is accurate, high quality and up-to-date Mandatory if DPIA is saved as activated | | `integrity__baselineSeverity` | string ("high" | "low" | "medium" | "very_high" | "very_low") | No | Represents the severity of a risk | | `privacyFramework__retention` | boolean | No | Is the retention period lawful and clearly defined? Mandatory if DPIA is saved as activated | | `availability__impactsComment` | string | No | Comment to add additional information about the impact | | `availability__threatsComment` | string | No | Comment to add additional information about the threat | | `confidentiality__plannedToms` | array | No | List of TOMs that are planned to be implemented to prevent confidentiality risk. At least one element is necessary DPIA is saved as activated | | `confidentiality__riskSources` | array | No | List of risk sources that confidentiality risk can have. At least one element is necessary DPIA is saved as activated | | `availability__baselineComment` | string | No | Comment to add additional information about the baseline risk of the availablity | | `availability__implementedToms` | array | No | List of implemented TOMs that applies to the availability risk. At least one element is necessary DPIA is saved as activated | | `integrity__baselineLikelihood` | string ("likely" | "limited" | "maximum" | "negligible" | "unlikely") | No | Baselinelikelihood | | `integrity__plannedTomsComment` | string | No | Comment to add additional information about planned TOMs to prevent integrity risk | | `integrity__riskSourcesComment` | string | No | Comment to add additional information about the integrity risk sources | | `availability__baselineSeverity` | string ("high" | "low" | "medium" | "very_high" | "very_low") | No | Represents the severity of a risk | | `integrity__residualRiskComment` | string | No | Comment to add additional information about the residual risk of the integrity | | `privacyFramework__transparency` | string | No | Field to describe what kind of notice information is given to data subjects about this processing, and how is it provided to the data subjects? Mandatory if DPIA is saved as activated | | `confidentiality__impactsComment` | string | No | Comment to add additional information about the confidentiality risk impacts | | `confidentiality__threatsComment` | string | No | Comment to add additional information about the confidentiality risk threats | | `integrity__residualRiskSeverity` | string ("high" | "low" | "medium" | "very_high" | "very_low") | No | Represents the severity of a risk | | `availability__baselineLikelihood` | string ("likely" | "limited" | "maximum" | "negligible" | "unlikely") | No | Baselinelikelihood | | `availability__plannedTomsComment` | string | No | Comment to add additional information about the planned TOMs | | `availability__riskSourcesComment` | string | No | Comment to add additional information about the availability risk sources | | `confidentiality__baselineComment` | string | No | Comment to add additional information about the baseline risk of the confidentiality | | `confidentiality__implementedToms` | array | No | List of TOMs that are implemented to prevent confidentiality risk. At least one element is necessary DPIA is saved as activated | | `availability__residualRiskComment` | string | No | Comment to add additional information about the residual risk of the availability | | `confidentiality__baselineSeverity` | string ("high" | "low" | "medium" | "very_high" | "very_low") | No | Represents the severity of a risk | | `integrity__implementedTomsComment` | string | No | Comment to add additional information about implemented TOMs to prevent integrity risk | | `integrity__residualRiskLikelihood` | string ("likely" | "limited" | "maximum" | "negligible" | "unlikely") | No | Residualrisklikelihood | | `availability__residualRiskSeverity` | string ("high" | "low" | "medium" | "very_high" | "very_low") | No | Represents the severity of a risk | | `privacyFramework__dataMinimisation` | string | No | Field to explain if the data collected adequate, relevant, and limited to what is necessary concerning the purposes for which it is processed Mandatory if DPIA is saved as activated | | `privacyFramework__retentionComment` | string | No | Field to add comment on the retention period | | `confidentiality__baselineLikelihood` | string ("likely" | "limited" | "maximum" | "negligible" | "unlikely") | No | Baselinelikelihood | | `confidentiality__plannedTomsComment` | string | No | Comment to add additional information about planned TOMs to prevent confidentiality risk | | `confidentiality__riskSourcesComment` | string | No | Comment to add additional information about the confidentiality risk sources | | `privacyFramework__additionalComment` | string | No | Field to add more information related to the privacy framework of the DPIA | | `privacyFramework__purposeLimitation` | string | No | Field to explain the clear, specific and legitimate purpose of conducting the processing activity. Mandatory if DPIA is saved as activated | | `availability__implementedTomsComment` | string | No | Comment to add additional information about the implemented TOMs | | `availability__residualRiskLikelihood` | string ("likely" | "limited" | "maximum" | "negligible" | "unlikely") | No | Residualrisklikelihood | | `confidentiality__residualRiskComment` | string | No | Comment to add additional information about the residual risk of the confidentiality | | `confidentiality__residualRiskSeverity` | string ("high" | "low" | "medium" | "very_high" | "very_low") | No | Represents the severity of a risk | | `privacyFramework__dataRightsExercised` | string | No | Field to describe how do data subjects exercise their data subject rights? Mandatory if DPIA is saved as activated | | `confidentiality__implementedTomsComment` | string | No | Comment to add additional information about implemented TOMs to prevent confidentiality risk | | `confidentiality__residualRiskLikelihood` | string ("likely" | "limited" | "maximum" | "negligible" | "unlikely") | No | Residualrisklikelihood | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update employee by id **Slug:** `BORNEO_UPDATE_EMPLOYEE_BY_ID` Updates the information of an existing employee in the Borneo integration platform. This endpoint allows you to modify various details of an employee's record, including personal information, job-related data, and organizational relationships. It's primarily used for maintaining up-to-date employee records, reflecting changes in positions, departments, or personal details. The endpoint requires the employee's unique identifier and accepts a JSON object containing the updated information. While it offers flexibility in updating multiple fields, it's important to note that the email address must remain unique within the company. This tool should be used whenever there are changes to an employee's information that need to be reflected in the system, but should not be used for creating new employee records or for bulk updates. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `nif` | string | No | The NIF (Spanish Tax Identification Number) of the employee | | `name` | string | No | The name of the employee | | `email` | string | No | The email of the employee. Has to be unique within the company. | | `endDate` | string | No | Date when the employee end to work in your company | | `manager` | string | No | The employee"s direct manager. | | `surname` | string | No | The surname of the employee | | `position` | string | No | The position in the company of the employee | | `startDate` | string | No | Date when the employee began to work in your company | | `department` | string | No | The department of the employee | | `employeeId` | string | Yes | Identifier of the employee | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update headquarter details by id **Slug:** `BORNEO_UPDATE_HEADQUARTER_DETAILS_BY_ID` Updates the information for an existing headquarter in the Borneo integration platform. This endpoint allows you to modify various details of a headquarter, such as its name, address, and associated Tom IDs. It should be used when there are changes to a headquarter's information or when correcting existing data. The endpoint requires the headquarter's unique identifier and accepts a JSON payload with the updated information. It enforces strict validation rules to ensure data integrity and consistency across the platform. Note that while some fields are optional, others (name, city, address, and country) are mandatory and must be provided with each update request. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `city` | string | Yes | The locality of the headquarter | | `name` | string | Yes | The name of the headquarter | | `tomIds` | array | No | Tomids | | `address` | string | Yes | The address of the headquarter | | `country` | string | Yes | 2 letter code that identifies a country. | | `zipcode` | string | No | The zipcode of the headquarter | | `headquarterId` | string | Yes | The identifier of the headquarter | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update lopdp threshold by id **Slug:** `BORNEO_UPDATE_LOPDP_THRESHOLD_BY_ID` Updates the LOPDP (Likely Operational Privacy Data Protection) threshold settings for a specific threshold identified by the lopdpThresholdId. This endpoint allows you to modify various data protection and privacy compliance parameters related to data processing activities. Use this endpoint when you need to adjust risk assessments, update processing characteristics, or change the status of a threshold. The endpoint is crucial for maintaining up-to-date privacy impact assessments and ensuring compliance with data protection regulations. Note that this endpoint only updates the threshold settings and does not perform any actual data processing or risk mitigation actions. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `status` | string ("activated" | "draft") | No | Status of the threshold. Can be draft or activated. | | `comment` | string | No | Additional information related to the Threshold | | `lopdpThresholdId` | string | Yes | Identifier of the Threshold | | `additionalComment` | boolean | No | Additionalcomment | | `largeScaleObservation` | boolean | No | Largescaleobservation | | `sensitiveOrSpecialData` | boolean | No | Sensitiveorspecialdata | | `rightsRiskProcessingData` | boolean | No | Rightsriskprocessingdata | | `freedomRiskProcessingData` | boolean | No | Freedomriskprocessingdata | | `innovativeTechnologiesUsed` | boolean | No | Innovativetechnologiesused | | `processingPersonalDataRisk` | boolean | No | Processingpersonaldatarisk | | `specialCategoryDataProcessed` | boolean | No | Specialcategorydataprocessed | | `systematicPersonalAssessment` | boolean | No | Systematicpersonalassessment | | `processingVulnerableDataSubject` | boolean | No | Processingvulnerabledatasubject | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update processing activity details **Slug:** `BORNEO_UPDATE_PROCESSING_ACTIVITY_DETAILS` This endpoint updates an existing processing activity in a data privacy management system. It modifies details about personal data processing, crucial for compliance with regulations like GDPR. Use it to update activity status, purpose, legal basis, data subjects, and more. Only 'active' and 'name' fields are required, but providing comprehensive information is recommended for accurate records. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `name` | string | Yes | Name of the processing activity | | `owner` | string | No | Owner | | `active` | boolean | Yes | Flag to create the processing activity as activated or draft | | `assets` | array | No | List assets ids related to the processing activity. | | `modelId` | string | No | Modelid | | `purpose` | string | No | Purpose of the processing activity | | `dataTypes` | array | No | Datatypes | | `infotypes` | array | No | List of info types related with the processing activity. | | `recipients` | array | No | List of recipients related with the processing activity. | | `companyRole` | array | No | Companyrole | | `dataSources` | array | No | Datasources | | `departments` | array | No | List departments related with the processing activity. | | `lawfulBasis` | array | No | List of Lawfulness types affected by a processing activity | | `dataSubjects` | array | No | List of Data Subjects affected by the processing activity | | `isDataStored` | boolean | No | Indicates if you store the data. | | `translations` | object | No | Translations | | `contactPerson` | string | No | Contact person for the processing activity. | | `additionalInfo` | string | No | Text to add more information about the processing activity | | `infotypeVolume` | string ("0-1000" | "1000-10000" | "10000-100000" | "100000+") | No | Ranges of the processed infotype volume. | | `managementMethods` | array | No | Managementmethods | | `infotypeCategories` | array | No | List of info types categories related with the processing activity. | | `showOnRopaDocument` | boolean | No | Showonropadocument | | `additionalInfoFiles` | array | No | List of uploaded file ids. | | `processingFrequency` | string ("is_systematic" | "not_systematic") | No | Data processing frequency. | | `processingActivityId` | string | Yes | Identifier of the Processing Activity | | `dataFlowRelationships` | array | No | Dataflowrelationships | | `retentionPeriod__unit` | string ("day" | "month" | "week" | "year") | No | Unit of time that is used for retention period | | `retentionPeriodComment` | string | No | Additional information related to the retention period | | `retentionPeriod__value` | integer | No | Value | | `areAccessRequestsManaged` | boolean | No | Indicates if the data subject access requests are managed. | | `processingFrequencyComment` | string | No | Processingfrequencycomment | | `processingActivitiesAsDataSources` | array | No | Processingactivitiesasdatasources | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update recipient details by id **Slug:** `BORNEO_UPDATE_RECIPIENT_DETAILS_BY_ID` Updates the information of an existing recipient in the Borneo integration platform. This endpoint allows you to modify various details of a recipient, including their name, business information, status, categories, roles, and data protection-related information. It's used when you need to change or update any aspect of a recipient's profile, such as updating their DPA status, changing their role, or modifying their data storage locations. This endpoint is particularly useful for maintaining up-to-date records of your business partners and ensuring compliance with data protection regulations. Note that some fields are required and must be included in every update request, while others are optional and can be omitted if no changes are needed. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `dpa` | string | No | The url to the DPA of the recipient | | `name` | string | Yes | Name of the recipient. Has to be unique, 2 different recipients can"t have the same name. | | `role` | array | No | Role | | `state` | string ("AK" | "AL" | "AR" | "AZ" | "CA" | "CO" | "CT" | "DC" | "DE" | "FL" | "GA" | "HI" | "IA" | "ID" | "IL" | "IN" | "KS" | "KY" | "LA" | "MA" | "MD" | "ME" | "MI" | "MN" | "MO" | "MS" | "MT" | "NC" | "ND" | "NE" | "NH" | "NJ" | "NM" | "NV" | "NY" | "OH" | "OK" | "OR" | "PA" | "RI" | "SC" | "SD" | "TN" | "TX" | "UT" | "VA" | "VT" | "WA" | "WI" | "WV" | "WY") | No | 2 letter code that identifies the state of the recipient. It only applies when the recipient country is US | | `status` | string ("archived" | "validated") | Yes | The status of the recipient. Can be archived or validated. | | `country` | string | No | 2 letter code that identifies a country. | | `dpaFiles` | array | No | List of uploaded file ids. | | `dpaStatus` | string ("attached" | "notRequired" | "requested") | No | The status of the DPA of the recipient. Attached if the DPA is provided. Not required when it"s not necessary to provide the information. Requested when we ask for the DPA and we are waiting for it. | | `categories` | array | No | list of recipient category | | `recipientId` | string | Yes | Identifier of the Recipient | | `businessName` | string | No | Business name of the recipient | | `recipientState` | string ("active" | "assessment") | No | Recipientstate | | `subProcessorIds` | array | No | Subprocessorids | | `automationStatus` | string ("created" | "ignored" | "new") | No | Automationstatus | | `dataStorageLocation` | array | Yes | List of countries where the data related to this recipient are stored | | `recipientWarranties` | array | Yes | List of lawful basis types that applies to the recipient. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update recipient status via id **Slug:** `BORNEO_UPDATE_RECIPIENT_STATUS_VIA_ID` Updates the status and automation status of a specific recipient in the Borneo integration platform. This endpoint allows users to modify a recipient's overall status (archived or validated) and their automation status (ignored, created, or new). It's particularly useful for managing recipient data lifecycle and controlling how recipients are handled in automated workflows. The endpoint should be used when there's a need to change a recipient's status due to changes in their relevance or to adjust their interaction with automated processes. It's important to note that this endpoint only updates status information and does not modify other recipient details. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `status` | string ("archived" | "validated") | No | The status of the recipient. Can be archived or validated. | | `recipientId` | string | Yes | Identifier of the Recipient | | `automationStatus` | string ("created" | "ignored" | "new") | No | Automationstatus | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Update threshold by id **Slug:** `BORNEO_UPDATE_THRESHOLD_BY_ID` Updates an existing threshold in the Borneo integration platform with new settings and information related to data processing and compliance. This endpoint allows you to modify various aspects of a threshold, including its status, comments, and multiple boolean flags that define the characteristics of the data processing activities. Use this endpoint when you need to adjust the parameters of a threshold to reflect changes in data handling practices, compliance requirements, or to activate a draft threshold. The endpoint is particularly useful for maintaining up-to-date records of data processing activities and ensuring compliance with data protection regulations. Note that updating a threshold does not automatically apply the changes to ongoing data processing; it may require additional steps to implement the updated settings in your data workflows. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `status` | string ("activated" | "draft") | No | Status of the threshold. Can be draft or activated. | | `comment` | string | No | Additional information related to the Threshold | | `blacklist` | boolean | No | Indicates if the data processing is included in a black list | | `thresholdId` | string | Yes | Identifier of the Threshold | | `translations` | object | No | Translations | | `classifyingDataSubject` | boolean | No | Indicates if this data processing is assessing or classifying data subjects | | `automatedDecisionMaking` | boolean | No | Indicates if there is automated decision-making with legal effect, or similarly significant effect involved | | `largeScaleDataProcessing` | boolean | No | Indicates if is a large scale data processing | | `innovativeTechnologiesUsed` | boolean | No | Indicates if there are innovative technologies used | | `matchingMergingRecordsInvolved` | boolean | No | Indicates if there is matching or merging of the records involved | | `processingVulnerableDataSubject` | boolean | No | Indicates if there is processing of data of vulnerable data subjects | | `systematicMonitoringDataSubject` | boolean | No | Indicates if there is systematic monitoring of data subjects involved | | `largeScaleProcessingSensitiveData` | boolean | No | Indicates if the data processing is large scale processing of sensitive data. | | `monitoringPubliclyAccessibleAreas` | boolean | No | Indicates if the data processing is systematic and large scale monitoring of publicly accessible areas involved. | | `processingConfidentialSensitiveData` | boolean | No | Indicates if there is processing of confidential or sensitive data | | `preventDataSubjectsExercisingTheirRights` | boolean | No | Indicates if the data processing prevents the data subjects from exercising their rights, using a service or performing a contract | | `extensiveAutomatedEvaluationCharacteristics` | boolean | No | Indicates if the data processing involve any systematic, extensive and automated evaluation of personal characteristics with effect for the data subjects. | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not | ### Verify email with id and token **Slug:** `BORNEO_VERIFY_EMAIL_WITH_ID_AND_TOKEN` Completes the email verification process for a user account in the Borneo integration platform. This endpoint is called when a user clicks on the verification link sent to their email address. It validates the provided verificationId and token to confirm the user's email address. This is a crucial step in the user authentication workflow, ensuring that users have provided valid email addresses and helping to prevent unauthorized access. The endpoint should only be used once per verification attempt, as tokens are typically single-use and time-limited for security reasons. Note that this endpoint doesn't handle the initial request for email verification or resending verification emails; it's specifically for completing the verification process. #### Input Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `token` | string | Yes | Token | | `verificationId` | string | Yes | Verificationid | #### Output | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `data` | string | Yes | Data from the action execution | | `error` | string | No | Error if any occurred during the execution of the action | | `successful` | boolean | Yes | Whether or not the action execution was successful or not |