> For the complete documentation index, see [llms.txt](https://knowledgebase.fabricdata.com/studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.fabricdata.com/studio/integrations-and-apis/api-overview/common-use-cases.md).

# Common Use Cases

## Integrate Metadata System

### Sync Titles Between Systems

Use the API to synchronize records between Origin Studio and:

* Internal title management systems
* Rights management systems
* MAM (Media Asset Management) platforms
* Scheduling systems
* CMS or publishing platforms

#### **Typical Pattern**

1. A record is created or updated in Origin Studio.
2. An SNS event (`record.created` or `record.updated`) is triggered.
3. Your system receives the event.
4. Your system calls:

```
GET /v1/records/{id}
```

5. The full record is ingested into your internal system.

This ensures your downstream systems always reflect the authoritative source of truth.

***

## Automate Enrichment

### Trigger Enrichment Workflows

The API can be used to automate enrichment processes such as:

* Adding external IDs (EIDR, IMDb, TMDB)
* Populating localized metadata
* Updating workflow status after enrichment
* Triggering review or approval stages

#### Example Automation Flow

1. A new record is created (`workflowStatus: draft`).
2. Your system detects the `record.created` event.
3. Your integration calls a third-party enrichment provider.
4. Your system updates the record via:

```
PATCH /v1/records/{id}
```

5. Workflow status is updated to `enriched` or `ready_for_review`.

This eliminates manual enrichment steps and reduces operational overhead.

***

## Drive Supply Chain Automation

Use the API to:

* Automatically create placeholder records
* Update workflow phases based on delivery milestones
* Validate metadata completeness before publishing
* Sync asset availability from external systems

This reduces manual intervention and increases supply chain reliability.

***

## Build Custom Applications

Developers can use the API to:

* Build internal dashboards
* Create operational monitoring tools
* Build approval or review interfaces
* Integrate metadata into consumer-facing platforms

Because the API follows JSON:API standards, it integrates cleanly with modern frameworks and tooling.

***

## Event-Driven Architectures

Rather than polling the API repeatedly, customers can:

* Subscribe to SNS events
* Trigger updates only when changes occur
* Reduce unnecessary API calls
* Improve performance and scalability

Recommended approach:

Event notification → Fetch full record → Process update.