Giter Club home page Giter Club logo

plex-api-spec's Introduction

plex-api-spec's People

Contributors

adrfranklin avatar jnorris441 avatar johnhebron avatar katyatitkova avatar lukehagar avatar shawncatz avatar speakeasybot avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

plex-api-spec's Issues

Watchlist spec

Wondering if there's plans to add support for the watchlist-related api calls... or if you're open to me adding them.

Specifically looking for user watchlists (/library/sections/watchlist/all) with the user's token on the https://metadata.provider.plex.tv api

Optimized Version Movie

I don't see "Optimize version" anywhere.
Is it possible to optimize films via this interface API?

Allow interaction with providers

Providers from Plex (Tidal Music Integration, Watchlist) expose an almost identical API as Plex Servers.

However restrictions in the schema prevent these sdks from using a provider as an input.

For example one can set up an instance like so:

const discoverProvider = new PlexAPI({ accessToken: "TOKEN", serverURL: "https://discover.provider.plex.tv" });

However trying to interact with the watchlist library section ID ends up with an error

> await discoverProvider.library.getLibraryItems("watchlist")
Uncaught SDKValidationError: Input validation failed
    at Object.parse (file:///home/chris/.cache/deno/npm/registry.npmjs.org/@lukehagar/plexjs/0.13.2/lib/schemas.js:43:19)
    at Library.getLibraryItems (file:///home/chris/.cache/deno/npm/registry.npmjs.org/@lukehagar/plexjs/0.13.2/sdk/library.js:512:35)
    at <anonymous>:1:41

Looking the schema, the input is restricted to a number. Taking a peek at the code relaxing this to be a number or string should allow reading these provider libraries, which otherwise return the same API shape

Would it be possible to update the schema to allow for this possibility?

Marker missing in Metadata

Hi i noticed that the marker are missing which are under MediaContainer / Metadata / Marker

and they look like this

"Marker": [
    {
        "id": 8561,
        "type": "credits",
        "startTimeOffset": 6503812,
        "endTimeOffset": 6571812,
        "Attributes": {
            "id": 8561,
            "version": 4
        }
    },
    {
        "final": true,
        "id": 8561,
        "type": "credits",
        "startTimeOffset": 6593812,
        "endTimeOffset": 6619792,
        "Attributes": {
            "id": 8561,
            "version": 4
        }
    }
]

they hold information like when the credits start.

im not shure how to add them in an merge request

additional information for the plex api

Hi,

I am currently working on a project that makes use of the plex apis and am currently generating a http client from this library, and just wanted to pop in and give some additional information based on some data I have found myself.

So just off the top of my head for what I am currently doing, I can think of 2 additions that change or add to the data you currently have.

  1. One being includeElements set to Stream for the endpoint /library/metadata/<ratingKey>/children which adds the Media section to the data, which is not currently present in your response.

  2. Another new endpoint you don't have yet is /statistics/resources which allows returning resources like cpu/ram stats. What I have for this one is: https://github.com/petio-team/petio/blob/dev/server/src/services/plex/serverInfo.ts

  3. Same as number 2, though using bandwidth endpoint: /statistics/bandwidth which returns bandwidth data. What I have for this one is: https://github.com/petio-team/petio/blob/dev/server/src/services/plex/bandwidth.ts

Let me know if you want me to create a PR for this or not, hope this helps a bit. I can continue to make issues and prs about other endpoints I found, if this is acceptable.

Support for version 1 of plex tv api

Version 2 of the plex tv api does not contain all the information that the version 1 does. For example /api/v2/friends endpoint seems to always have sharedServers array as empty, while the version 1 endpoint /api/users does maintain which servers the users are in, which is useful for people like me, where syncing the users in to my app, I am able to filter out users a person is friends with but not in the same server connected to my app.

I am sure there are plenty of other endpoints in version 1 that contains data that is not yet in version 2, so it would be nice if we could document both?

languageOverride missing in metadata

languageOverride is missing from MediaContainer -> Metadata. It's only available if you've changed "Metadata language" of a library item to something other than "Library default" under "Advanced":
image

The format of langaugeOverride is a locale code string, e.g. sv-SE.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.