User 1

[tepid fulcrum]

hi! right now we don't have any websocket support, no. Happy to answer more if you have some more clarification

[harsh terrace]

Nah it's okay. I was really just hoping I could use your guys's links feature and then pull info about stuff via websockets instead of dealing with all this webhook craziness.

Would also mean that I wouldn't need to create an express server and all of that if it was like that

[rough sedge]

Hi! I'm taking over this thread.

For most integrations we strongly recommend using webhooks. And yes like my colleague said, we don't support websocket.

[harsh terrace]

So does that mean I have to provide Stripe with a domain for the webhooks to go to? Cause I assume it would not take a raw IP of a server...

[rough sedge]

I'm not sure I understand your question, since like I said above we don't support websocket.

[harsh terrace]

*webhooks, sorry

[rough sedge]

Yes when you create your webhook endpoint you need to provide a publicly accessible URL where Stripe will send then events.

[harsh terrace]

And that can't be an IP?

[rough sedge]

I'm not sure, I would recommend to do a quick test to see if that works.

[harsh terrace]

Would it be insecure to do it that way?