Skip to main content
Documentation

Contact support

Docs

Bridge architecture

How official Korvix3D bridges fit together with Asset Hub and your DCC. This is not a guide for building your own third-party API clients.

Placeholder image — replace with an architecture diagram when ready.

Bridge components

Connection to Asset Hub

Each bridge coordinates with Korvix3D Asset Hub for:

  • • Sign-in and session (via the desktop app)
  • • Asset discovery and downloads
  • • Shared folders and import-ready files
  • • Error reporting and updates

Inside the DCC

Native UI and scripting hooks for:

  • • Browsing and importing assets
  • • Progress and file placement
  • • Settings that match each host application

Typical flow

1

You sign in

You authenticate in Korvix3D Asset Hub. The bridges rely on that session rather than exposing separate API keys.

2

Browse in the DCC

The bridge shows library content and download/import actions in the host software.

3

Import

Assets are delivered through the paths Asset Hub and the bridge agree on, then opened in your scene.

What we do not document here

Korvix3D does not publish a public REST or GraphQL API for external integrations. Automation inside a DCC should use that application's own scripting (for example Blender's bpy) together with the bridge UI, not undocumented HTTP endpoints.

See the FAQ for a short policy on third-party APIs.