Changes planned for JSON-RPC (Router 4.x) API?

[Quidn]

Hi,
There were JSON-RPC (Router 4.x) API documentations on https://dev.gl-inet.com/ but currently it's closed and for almost all this year.

Because of I'm going to use the JSON-RPC API, so I'd like to know if there are any plans for significant changes near soon, or if just the public website is closed.

To be clear, I'm not asking for API documentation, and just want to know if the current API will remain similar as now for some while.

Thanks.

[bruce]

Regarding the closure of the API, here is a before detailed reply.

Formal statement on Gl.iNet software going closed source?

The open source thing does change. The source code is still in github. Previously we have a builder to build the exactly firmware as the stock firmware but with user’s customizations. That is supposed to be used only by users for peronal use. But someone use that to build firmware, bypassing our restrictions e.g. country code, vpn etc for commerical use. That brings huge risk for our business and users. We removed that builder from github. The source code, sdk, imagebuilders are still in gith…

Formal statement on Gl.iNet software going closed source?

Everyone can benefit from open source. It is called licensing. If you use open source code, you need to do it according to the license. You can check open source license thing in other website. GL.iNet used open source and released source code as required. But for some programs we developed, we may or may not release source code. For example our api and UI are never open source. We released some tools so that users can build firmware easier. These are only for personal use and can not be used…

The APIs will not be change in small versions (such as v n.1.1-n.9.9), but probably added or deleted in major versions (v 3.x.x, 4.x.x, 5.x,x)

[Quidn]

My first thought after reading your answer was, how could that issue be related to my question, but soon I see. Thanks for the hint! Now I understand why it have been closed for this long.

So since it's closed for an indisputable reason unrelated to any dev issues, I think it'd be better to have some explains that it won't be open for a while on the website for people looking for the API documentation. As it's now, people might consider that GL.iNet dev and support is bad or stopped. (Like this)

Thanks to you I got peace of mind to use the current API without considering about big changes.

[bruce]

Thank you.
If you request any API information, please contact support@gl-inet.com to obtain it.