Overview: Automation and interoperability

Media-server integrations use supported APIs and event mechanisms to connect server state with operations in other applications.

An integration needs to know both what the server observed and what its own action completed. A playback event, an accepted API request and a changed room scene are related results, but they belong to different stages.

The API branch covers requests, credentials and current state. Events and integrations cover delivery, retries, permissions and extension lifecycles. These topics help build an Emby-related workflow that remains understandable when messages repeat, a connection drops or another system applies its own access rules.

• Media server APIs
  Media-server APIs expose supported operations and state through defined request, credential and response contracts.

• Events and integrations
  Events and integrations connect server observations with accepted work and effects in other application lifecycles.