What's the difference between termination-api and api/v1?

Sorry if this is a silly question. I don’t know much at all about APIs, so I’m not entirely sure whether there are any search terms I could use to find the answer to my question myself.

I was just looking through some of the more recent API threads when I stumbled upon anoek’s comment in the Game dump thread.

He suggests using https://online-go.com/termination-api/game/<id>. But what’s the difference between this and https://online-go.com/api/v1/games/<id>? If I navigate to them, I can see an obvious visual difference, and that the json is smaller in that it has fewer fields - same with termination-api/player/<id> as opposed to api/v1/players/<id>.

Is the termination-api not a Rest api? Is it faster, or less taxing on the server? Does one of these contain data that is generated on demand, while the other does not?

6 Likes

I don’t know either.
The only thing I know is that I was aware of termination api existence way later than v1, so I believe that’s a newer thing.
Many of my queries are still using v1.

2 Likes

The termination-api endpoint is much faster and easier on the servers, the v1 stuff exists for backwards compatibility but should be avoided in general.

4 Likes

Maybe termination-api should have a friendlier and more inviting name? :slight_smile:

4 Likes

Maybe… but it also sounds pretty cool as-is :stuck_out_tongue_winking_eye:

2 Likes

I’m imagining some kind of dystopian remote-control electric chair.

1 Like

Is there currently a ​ api/v2 ? ​ ​ ​ If no, perhaps the
termination-api ​ should be renamed to that.

1 Like

Now I’m imagining https://online-go.com/termination-api/player/<id> ordering a drone strike on a particular user

2 Likes

When we ban users, we mean it.

2 Likes