---
title: Introduction | Avara
description: Who integrates with Avara, which product path to follow, and where configuration is spelled out for AutoScribe, Viewer, and Express.
---

This section is for **integrating partners**: PACS companies, EHR/RIS companies, distributors with their own **software platform**, and IT teams wiring Avara into an existing system.

You sell or operate imaging or clinical software. AutoScribe, Viewer, or both should show up inside that product — studies created from your system, webhooks back to your archive or RIS, users opening Avara without a second login when you want that.

Clinical Platform sites do not need a separate integration. Start from the [Clinical Platform overview](/clinical-platform/overview/index.md). Distributors who only do support and resale, without a software platform, should use a **separate Avara organization per customer**, not Express.

## Which product to integrate

Pick the track that matches what you are embedding. Each product spells out **what to configure** (API key, which webhooks, when to create studies) so you do not implement every endpoint.

[**AutoScribe**Reporting and dictation. Configure an API key, pick webhook profiles, create studies if you are not on Avara PACS, invite readers.](/integration/autoscribe/introduction/index.md)[**Viewer**Viewing only — no reporting. Three webhooks at most. Create studies if DICOM lives in your archive.](/integration/viewer/introduction/index.md)[**Avara Express**Sell AutoScribe and/or Viewer as a service to your customers. Deep integration — expect a real API implementation to fit your data model.](/integration/express/introduction/index.md)[**Clinical Platform**No partner integration to stand up. Use the product overview.](/clinical-platform/overview/index.md)

## How configuration is spelled out

For AutoScribe and Viewer, start at **API Config** (create the key, webhook URLs, signing secret), then **What webhooks should I configure**. That page maps **who you are** (PACS with your own archive vs EHR/RIS on Avara PACS, with or without Avara Viewer) to the endpoints to set. Leave the rest blank.

Express adds tenants on top of those products: enable Express, create customers, add users, attach `expressCustomerId` on study create. Isolation is membership-based — [Isolation](/integration/express/isolation/index.md).

### AutoScribe

[**API Config**Create the AutoScribe API key and set webhook URLs.](/integration/autoscribe/api-config/index.md)[**What webhooks should I configure**Three profiles: PACS without Avara Viewer, PACS with Avara Viewer, EHR/RIS with Avara PACS.](/integration/autoscribe/what-webhooks-should-i-configure/index.md)[**Create studies**Required when you are the archive and not using Avara PACS.](/integration/autoscribe/create-studies/index.md)[**Temporary access views**Open AutoScribe (or viewer-only) from your app without a dashboard login.](/integration/autoscribe/temporary-access-views/index.md)

### Viewer

[**API Config**Create the Viewer API key and set the three Viewer webhook URLs.](/integration/viewer/api-config/index.md)[**What webhooks should I configure**Two profiles: your DICOM archive plus Avara Viewer, or EHR/RIS with Avara PACS.](/integration/viewer/what-webhooks-should-i-configure/index.md)[**Create studies**Required when you are the archive and not using Avara PACS.](/integration/viewer/create-studies/index.md)[**Temporary access views**Open Viewer from your app with a short-lived URL.](/integration/viewer/temporary-access-views/index.md)

### Avara Express

[**Introduction**Who Express is for, billing, and how to enable it.](/integration/express/introduction/index.md)[**Isolation**Admins see everything. Members see only the customers they belong to.](/integration/express/isolation/index.md)[**Customers**Create and manage Express customers.](/integration/express/customers/index.md)[**Studies**Attach expressCustomerId so tenant members can see the exam.](/integration/express/studies/index.md)

## Objects, pixels, and the API

Identifiers (`stu_…`, `usr_…`, `cus_…`) and the shape of studies, users, and Express customers are on the **API Data Model** page. How the viewer actually fetches DICOM — presigned blob URLs, not DICOMweb — is on **Loading Viewer Data**. Method names, request fields, and generated SDK snippets are on the **API Reference**.

[**API Data Model**Branded IDs, AutoScribe vs Viewer objects, and Express customer fields.](/integration/api-data-model/index.md)[**Loading Viewer Data**Presigned blob URLs, just-in-time parse, Avara PACS vs your archive webhook.](/integration/loading-viewer-data/index.md)[**API Reference**Every endpoint and SDK operation — docs.avarasoftware.com/api.](/api/index.md)