Here’s the API docs for the HTTP API. If you want to know the low level endpoints, just click the defined in links. We use that javascript / typescript API client as the reference, but it defines every endpoint call and response types, and someone could easily build another client for other programming languages using it as the reference.
There’s a world of difference between can and wants to. And as I already pointed out, the existing client is incomplete in important ways, like error handling. So even if I was excited to fuck around figuring out how it works, it still wouldn’t be as good as actual documentation.
I get that this isn’t important to you, but continuing to insist that it’s documented when it objectively isn’t is indefensible. Just say that you don’t care and let folks decide whether they want to deal with it or walk.
Here’s the API docs for the HTTP API. If you want to know the low level endpoints, just click the defined in links. We use that javascript / typescript API client as the reference, but it defines every endpoint call and response types, and someone could easily build another client for other programming languages using it as the reference.
I’ve had this conversation with you before. Nothing has changed since then, and all my arguments stand.
If you can’t read through a well documented api and convert it to another language, I don’t know what to tell you.
There’s a world of difference between can and wants to. And as I already pointed out, the existing client is incomplete in important ways, like error handling. So even if I was excited to fuck around figuring out how it works, it still wouldn’t be as good as actual documentation.
I get that this isn’t important to you, but continuing to insist that it’s documented when it objectively isn’t is indefensible. Just say that you don’t care and let folks decide whether they want to deal with it or walk.