> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livingsecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Data Exports

> Retrieve Living Security data through the Public API for custom reporting, data warehouses and security tools.

Use the Living Security Public API to retrieve data for your reporting system,
data warehouse or security tools. Your integration makes requests to the API
and sends the results to the destination you manage.

For messages to people, use
[communication channels](/features/communications/channels/overview).
For a reporting connection without custom code, see
[Power BI](/developers/v1/powerbi).

## Build an export

<Steps>
  <Step title="Choose the data you need">
    Start with a published API resource or a
    [report recipe](/developers/v1/reports/per-person-compliance).
    Select the fields and filters your destination needs, and choose a refresh
    interval that fits your reporting requirements.
  </Step>

  <Step title="Authenticate your integration">
    Create a service account for the export and grant only the permissions it
    needs. Follow the [API quickstart](/developers/v1/quickstart) to make your
    first request with an API key. See
    [Authentication](/developers/v1/authentication) if your security policy
    requires OAuth access tokens.
  </Step>

  <Step title="Read all pages">
    Follow the [pagination guide](/developers/v1/pagination) to collect a
    complete result set. Keep filters consistent while following a cursor,
    handle cursor expiry, and account for records changing during a read.
  </Step>

  <Step title="Schedule and monitor refreshes">
    Schedule requests in your integration and follow the
    [rate-limit and retry guidance](/developers/v1/rate-limits).
    Record refresh outcomes and request IDs so you can investigate failed or
    incomplete exports. Keep credentials and exported personal data out of logs.
  </Step>
</Steps>

## Protect exported data

Use the [regional API host](/developers/v1/regions) for your organization.
Review the destination's access controls and retention policy before sending
personal data to it. Store API credentials in a secret manager, and rotate or
revoke them when the integration changes.

When requesting help with an export, include the operation, HTTP status and
`Request-Id`. Do not include API keys, access tokens or exported personal data.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.