My API is quite simple, you connect to api.websocket.email/v1/subscribe with a websocket an an HTTP header. It just saves a bit of time when you don't want to r

My API is quite simple, you connect to api.websocket.email/v1/subscribe with a websocket an an HTTP header. It just saves a bit of time when you don't want to read specs like that, maintain a server, or setup credentials. At some point it makes sense to setup your own servers though. It's up to the individual to decide. I just wanted a way to write some unit tests, had to setup an email server, then made my test interface public.