Skip to main content
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
  2. Authentication
  3. API Reference
  4. Partner Integrations

Who does what

  • Your team owns implementation, release, and production monitoring.
  • Obvlo provides destination content, API documentation, and onboarding support.
QuestionAnswer
Where should developers start with API delivery?Start with API overview, then Authentication, and API Reference.
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.