sessions.getSessionHistory filter param does not work?

[BobWithHair]

Running this code:

const response = await plexAPI.sessions.getSessionHistory(
  'viewedAt:desc',
  undefined,
  { viewedAt: '>=1723511329' }
);

Sends this url: http://<MY_PLEX_SERVER>/status/sessions/history/all?sort=viewedAt%3Adesc

So as you can see, the filter is completely omitted. The documentation doesn't say anything outside of:

The lib's source code defines the Filter type as an empty object:

The only thing helping to try and figure this out is inspecting the Network tab when going in Plex's history page:

[BobWithHair]

Updated to 0.23.0 and this still does not seem to work. Am I doing it wrong or is it a bug?

[LukasParke]

Hey @BobWithHair,

Can you confirm that the local package is up to date?
I can confirm the most recent regeneration contains the updated filter value:

export type GetSessionHistoryRequest = {
  /**
   * Sorts the results by the specified field followed by the direction (asc, desc)
   *
   * @remarks
   */
  sort?: string | undefined;
  /**
   * Filter results by those that are related to a specific users id
   *
   * @remarks
   */
  accountId?: number | undefined;
  /**
   * Filters content by field and direction/equality
   *
   * @remarks
   * (Unknown if viewedAt is the only supported column)
   */
  filter?: QueryParamFilter | undefined;
  /**
   * Filters the results based on the id of a valid library section
   *
   * @remarks
   */
  librarySectionID?: number | undefined;
};

[BobWithHair]

Hey @LukeHagar! Sorry, haven't been working on my project in the last week or so. So, yes my package is up to date. Just re-updated it to the most recent 0.23.5

I did and still do see that GetSessionHistoryRequest type, but the QueryParamFilter type is only an empty object:

.

But could you comment on the syntax I used for the filter in my original post? Because it is not so simple to figure out what syntax is expected to make the filter work

[LukasParke]

Triage update:

• Labeled as bug (filter parameter appears to be ignored in sessions.getSessionHistory).
• I don’t see enough information to mark this as a duplicate right now.

This issue has also been inactive for a long time (>90 days).
Could you please retest with the latest release and share a minimal reproducible example (exact call + observed request URL/response)? If this is still reproducible, we can keep it open and actionable; otherwise we can close it as resolved.