On the listen side, you can run `stripe listen --print-json` which will output the entire object.

You can also resend events by doing `stripe events resend <event_id>`.

We'll see about documenting both better!

Hi all! I'm one of the folks who's been working on this for the past few months. I'm happy to answer some questions about the CLI or how it was built (using Go and websockets for pushing data). If you have any ideas or feedback feel free to email me directly too! [email protected] -- We'd love to hear how you're using the CLI and what you'd like to see in the future.

Super minor complaint, but when I suspend/lose connection for a while and it restores, I have to restart the CLI to resume receiving events.

We're looking into improving the disconnect/reconnect flow! Hopefully will have some progress on that soon.

Does stripe PGP encrypt everything on top of TLS? Question for cli and browser

Does Stripe have a public WebSocket API?

We don't, this is using a private API.

Curious what your use case is.

My guess: Money Laundering.

You could certainly pay less than ~$20,000 in Stripe/CC fees to move $1M if your motives were on the up and up. Especially if you were doing it regularly.

I'm going to try to do some follow up posts in the next few weeks around building this and I'll work to incorporate some of that in there. It was definitely interesting getting this going.

As bpicolo said, lots of Python.

The API itself is a Python service running on Pyramid/uWSGI. Our focus on services internally means that the API delegates our REST requests to other internal services when resolving the data.

As far as the GraphQL implementation, we used Graphene (graphene-python.org) for that.

Hey! I fixed reviews so the example should work now and pushed out a change to the developer site to fix a broken example I noticed.