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

# Livry APIs: Management API and Serving API Overview

> Livry exposes a Management API for administering Organizations, tokens, and Applications, and a Serving API that delivers resolved themes at runtime.

Livry exposes two distinct APIs. They serve different callers, have different performance characteristics, and authenticate differently.

## Management API

Administers your Livry resources — Organizations, tokens, Applications, Tenant configuration.

Called from your backend, your CI pipeline, or your own admin tooling. Authenticated with an OAuth 2.0 bearer token for the `https://api.livry.dev` audience.

Low volume, strongly consistent, and the surface you'd script against when automating brand onboarding.

## Serving API

Returns the resolved theme for an Organization — the default theme with that brand's overrides already applied.

Called by your application at runtime, typically from the browser, at high volume and through a CDN. Authenticated with signed URLs rather than bearer tokens.

<Info>
  Keep the two straight when designing your integration: administration goes through the Management API from trusted server-side code, and runtime theme delivery goes through the Serving API via signed URLs.
</Info>

<Card title="Authentication" icon="key" href="/api/authentication">
  How to authenticate against each API.
</Card>