Any chance the user_badge webhooks could include username along with user_id? Currently the payload for a user_badge event looks like this: { "user_badge": { "id": 123456, "granted_at": "2026-09-25T14:54:42.073Z", "created_at": "2026-09-26T05:34:12.965Z", "post_id": 234567, "p…

FWIW, my workaround for non-standard webhooks or when I need additional data is to do it via Workflows and then send that to n8n.

[image] burke: I’m creating an external service that I was hoping to trigger when specific badge(s) are granted; however, it needs the username and badge webhooks only returns user IDs. Fwiw, fetching username from user id is just one API call away, unless you’re manually granting thousands o…

[image] putty: FWIW, my workaround for non-standard webhooks or when I need additional data is to do it via Workflows and then send that to n8n. Thanks! I’ll look into Workflows.

[image] itsbhanusharma: Fwiw, fetching username from user id is just one API call away, unless you’re manually granting thousands of badges in an instant, you should be fine with the default API limits. That’s great to hear! Could you please provide details about that one API call that isn’t /…

What’s the issue with an admin API key? This is supposed to be a background job ig?

[image] itsbhanusharma: What’s the issue with an admin API key? This is supposed to be a background job ig? Principal of Least Privilege. This external service will be running on another server and only needs read access to Discourse to do it’s job. The fewer master keys floating around acros…

This brings up the interesting point of why isn’t there a public-facing endpoint to get a user by id that shows only public fields, if login_required is not selected. It would be useful, no? I wonder why it was not made. Or maybe only logged in users could get such a privilege, but either way, there…

This is because for all matters and purposes user IDs are essentially an internal convention in discourse and we are expected to rely on usernames that are much more prominent across the board.

Which brings us back to the original request. The webhook should adhere to that concept and send the username, not the user ID.

[image] RGJ: Which brings us back to the original request. The webhook should adhere to that concept and send the username, not the user ID. Agreed! This seems like the best solution. Adding username and granted_by_username and deprecating user_id and granted_by_id could allow for a non-break…

Peut-on inclure les noms d'utilisateur dans la charge utile du webhook user_badge ?

Assistance produit

RGJ (Richard - Communiteq) Septembre 30, 2026, 7:13 10

Ce qui nous ramène à la demande initiale. Le webhook doit respecter ce concept et envoyer le nom d’utilisateur, et non l’identifiant utilisateur.

Sujet		Réponses	Vues
Webhooks feedback Development	33	11400	Mars 21, 2017
Grant a custom badge through the API Integrations rest-api , how-to	9	8064	Novembre 18, 2023
Improved badge granting workflow Feature badges , completed	29	5254	Janvier 23, 2018
Wishlist: visual cue for "user got a badge for this post" Feature badges	36	2200	Décembre 5, 2024
Bulk Award a badge to a set of users Announcements badges , new-feature	28	6534	Mars 31, 2025

Peut-on inclure les noms d'utilisateur dans la charge utile du webhook user_badge ?

Sujets connexes