Borneo

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.