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

# API

> Plan API onboarding from first call to production readiness.

Use this guide when your team wants to deliver Obvlo content through your own website, app, or internal systems.

## What this product is

API delivery gives your developers direct access to destination content so it can be used in your own applications, websites, and workflows.

## Best use case

Use API delivery when you need a custom user experience, or when Obvlo content needs to flow into your existing products.

## What to align before setup

* Organisation and destination scope for launch
* Ownership for API implementation, testing, and monitoring
* Environment and release plan for integration rollout
* Reporting and monitoring expectations after launch

## Start path for developers

Use the Developer pages below as your implementation path:

1. [API overview](/developer-docs/api/overview)
2. [Authentication](/developer-docs/api/authentication)
3. [API Reference](/api-reference/introduction)
4. [Partner Integrations](/product/delivery/partner-integrations)

## Who does what

* **Your team** owns implementation, release, and production monitoring.
* **Obvlo** provides destination content, API documentation, and onboarding support.

## Related FAQs

| Question                                              | Answer                                                                                                                                                                |
| ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Where should developers start with API delivery?      | Start with [API overview](/developer-docs/api/overview), then [Authentication](/developer-docs/api/authentication), and [API Reference](/api-reference/introduction). |
| When should we choose API instead of hosted channels? | Use API when your team needs full control over frontend behaviour across your own apps or services.                                                                   |
| How should we handle rate limits and failures?        | Implement retries, validation checks, and logging as part of your production integration standards.                                                                   |

## Related pages

* [Getting Started](/getting-started/start-here)
* [Platform overview](/product/platform-overview)