Ko-Fi support possible?

[TheRealDadbeard]

Hy,

just stumpled upn this and was wondering if Ko-Fi support is feasible with this? Either via their official API or maybe in conjucntion with streamer.bot?

[RealityRipple]

Short answer: barely possible, not friendly, likely confusing for users.

---

Long answer:

Unfortunately the official API uses webhooks, not websockets, which makes this significantly messier. Additionally, there's no auth method like there is for Streamlabs and StreamElements, where I'd just show an "authorize through ko-fi" button, you'd log in, and I'd be able to set everything up in the background to integrate.
Instead, it would require you to manually set the webhook URL in the Ko-Fi settings page, and then submit Ko-Fi's verification token through a form on my site.
It's also not feasible if you're already using the API for something else, as you can only have one hook url at a time.

Likewise, streamer.bot's message system doesn't have any friendly auth methods, and instead relies on local-host communication over custom set ports. This is absolutely awful for smooth integration purposes, and would only work for advanced users. It would also require anyone who wants to use Ko-Fi alerts to download and regularly run a bot they otherwise would have no need of (assuming it's not the streamer's bot of choice).

And Zapier would cost me a monthly fee for more than 100 messages a month for everyone that uses it, as far as I can determine. I'm also not sure if they have websocket support or a decent auth system, but the cost makes that a moot point anyway.

---

It's also too bad they don't let you customize the chat bot messages, or you could just add a kappagen command to the start of the chat alert.

I'll keep this issue open, in case Ko-Fi adds websockets (or server-sent events or whatever) with an auth method for third-party sites.

---

Edit: for good measure, I submitted some feedback asking Ko-Fi to consider adding either websocket support, or multiple webhook URLs and some more seamless method of adding a URL and retrieving a verification token, to streamline what's currently a very manual process. We'll see if they think it's a decent suggestion.