> ## 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.

# Developer Hub

> Manage service accounts, API keys, and request logs for the Living Security Public API from one workspace.

The Developer Hub is the workspace for operating your organization's Public
API access. It lives in the Dashboard under **Settings → Integrations &
Developers → Developer Hub** and brings together three things: service
accounts, the API keys they hold, and the request logs those keys produce.

<Note>
  If you cannot see the Developer Hub, ask your organization's administrator
  to check your access or contact Living Security Support.
</Note>

New to the API? Start with [Authentication](/developers/v1/authentication) to
choose an API key or OAuth client credentials. You do not need OAuth for an
API-key integration. The [quickstart](/developers/v1/quickstart) walks from
creating a service account to your first authenticated request with an API key.

## Service accounts

A service account is a named identity for an integration. It can own API keys
and OAuth clients. Each
account carries its own set of granted permissions (for example `entity:read`
or `reporting:read`), which acts as the ceiling for every credential created under
it. Create one account per integration, enable or disable it as a unit, and
edit its permissions at any time.

## API keys

API keys authenticate requests to the Public API. Keys are created on a
service account's detail page and are always scoped to a subset of that
account's permissions. Every key has an identifier starting with `ak_` and a
secret starting with `lsk_live_` that is shown **once** — at creation or
rotation. Expiration is mandatory, rotation comes with an overlap window so
you can roll deployments without downtime, and revocation is immediate. A
key authenticates only on the organization's regional `/v1` host. See
[Regions](/developers/v1/regions).

## Expiry notifications

When the feature is enabled for your organization, the **Expiry notifications** tab lets you choose which admins are warned before service-account API keys expire, which channels to use, and how many days ahead to notify. Service accounts can override recipients on their own **Expiry notifications** tab. See [API keys](/developers/developer-hub/api-keys#expiry-notifications).

## Request logs

The **Request logs** tab shows your organization's Public API traffic:
request counts, error rate, and rate-limited requests over the last 24
hours, plus a searchable log of individual requests. Filter by service
account, API key, method, status class, decision, or time range — or look up
the `Request-Id` returned in an API response to trace exactly how a request
was handled.

## Guides

<CardGroup cols={2}>
  <Card title="Authentication" href="/developers/v1/authentication">
    Choose API keys or OAuth and understand service-account identity.
  </Card>

  <Card title="Service accounts" href="/developers/developer-hub/service-accounts">
    Design per-workload identities and manage their lifecycle.
  </Card>

  <Card title="API keys" href="/developers/developer-hub/api-keys">
    Create, scope, rotate, and revoke credentials safely.
  </Card>

  <Card title="Request logs" href="/developers/developer-hub/request-logs">
    Trace traffic, filter by credential, and debug by request ID.
  </Card>

  <Card title="API quickstart" href="/developers/v1/quickstart">
    From zero to your first authenticated request.
  </Card>

  <Card title="Power BI" href="/developers/v1/powerbi">
    Connect Power BI to `/v1`, choose operational vs reporting grain, and refresh safely.
  </Card>
</CardGroup>


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