Emby Emby Emby Learn
  • Emby Home
  • Video
  • Audio
  • Media Files
    • Subtitles and captions
    • Photos and images
    • Metadata and discovery
    • Libraries and media collections
    • Playback and streaming
    • Media hardware acceleration
    • Displays and AV connections
    • Live TV and recording
  1. Emby Learn
  2. Automation and interoperability
  3. Media server APIs
  4. Requests and responses
Search Results for

    Show / Hide Table of Contents

    Overview: Requests and responses

    API requests and responses connect HTTP operations with typed payloads and bounded observations of result sets.

    HTTP describes the exchange, JSON represents its data, and pagination limits how much of a query result arrives at once. Each layer has its own meaning and failure conditions. The pages here keep them distinct so a parsed response is interpreted as the intended operation's result.

    • HTTP API requests
      An HTTP API request combines a method, target, headers and optional content, while the response status and operation contract define its result.

    • JSON payloads
      JSON represents typed values in a text interchange format, while a schema defines field meanings, units and treatment of missing or null data.

    • API pagination
      Pagination returns bounded portions of a result set, but offsets refer to the list as observed and can shift when its contents change.

    References

    • RFC 9110: HTTP semantics
    • RFC 8259: JSON
    • Emby user item queries
    2026 © EMBY LLC. Please see our terms of use and privacy policy.
    Back to Top