Dev Doc improvement

[HawkXP71 118]

The current root page of the dev documentation should have a "Plugin C# API" and "Server C# API" in its "Emby SDK" TOC on the left hand side.

Right now, to find either API, you have to realized its under the developer home (not obvious), then find the "worth a look" link in the "Emby Server .NET API" group.

It would be great if there was a quick link at the top to get to the "Documentation/reference/index.html" page

Scott

[Luke 42988]

@softworkz

[softworkz 5368]

2 hours ago, HawkXP71 said:

The current root page of the dev documentation should have a "Plugin C# API" and "Server C# API" in its "Emby SDK" TOC on the left hand side.

Right now, to find either API, you have to realized its under the developer home (not obvious), then find the "worth a look" link in the "Emby Server .NET API" group.

It would be great if there was a quick link at the top to get to the "Documentation/reference/index.html" page

Scott

 

Hi Scott,

thanks for the suggestion! We are welcoming suggestions as there's always room for improvements and we don't want to miss any opportunity for getting better.

Yet, in this case, I'm not quite sure what you're up to, because there's nothing like two different C# APis:

• There's a .NET API for developing server plugins (C# is  .net language of course)
• And there's a REST API for accessing Emby Server via  a remote connection
  For that REST API access, we are providing a range of ready-made implementations in various programming languages - including C#,
  but that's not a C# API, these are just REST API clients we provide for various languages

[HawkXP71 118]

On 8/27/2026 at 3:21 PM, softworkz said:

 

Hi Scott,

thanks for the suggestion! We are welcoming suggestions as there's always room for improvements and we don't want to miss any opportunity for getting better.

Yet, in this case, I'm not quite sure what you're up to, because there's nothing like two different C# APis:

• There's a .NET API for developing server plugins (C# is  .net language of course)
• And there's a REST API for accessing Emby Server via  a remote connection
  For that REST API access, we are providing a range of ready-made implementations in various programming languages - including C#,
  but that's not a C# API, these are just REST API clients we provide for various languages

Sorry if I was confusing

 

My goal? I want to be able to get to the server side C# api documentation as soon as possible. Not the REST api

I was hoping it could be added to the tree explicitly on the LHS