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, "post_number": 1, "badge_id": 123, "user_id": 456, "granted_by_id": -1, "topic_id": 56789 } } Getting the username for the user_id (and granted_by_id if it’s not -1) requires an additional call to /admin/users/{user_id}.json, which not only requires additional requests, but also requires admin privileges as far as I can tell. Is there a way to get username for a given a user_id using an API key without needing admin privileges? 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. :confused:

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.

[Bild] 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 of badges in an instant, you should be fine with the default API limits.

[Bild] 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.

[Bild] 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 /admin/users/{user_id}.json (which requires admin privileges)? I wasn’t able to find an endpoint to do this with an API key that didn’t require admin privileges.

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

[Bild] 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 across infrastructure, the better.

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 should be some way to access it without the use of the admin endpoint… @burke A more onerous workaround would be to look at /groups/trust_level_0/members.json (or any more specific group) and find the user by their id, since that also contains the username.

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.

[Bild] 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-breaking transition period. Currently, if a badge is changed by the system (i.e., automatically), the webhook returns a granted_by_id of -1. What would be the equivalent for granted_by_username? "" (empty string) " " (a magic value that couldn’t be a username) null Nothing – i.e., omit granted_by_username from the payload if it was a system-driven event I would assume null or nothing would make the most sense.

Können Benutzernamen im Webhook-Payload von user_badge enthalten werden?

Produktunterstützung

itsbhanusharma (Bhanu Sharma) 28. September 2026 um 17:02 6

Was ist das Problem mit einem Admin-API-Schlüssel? Das soll doch eigentlich ein Hintergrundjob sein, oder?

Thema		Antworten	Aufrufe
Webhooks feedback Development	33	11483	21. März 2017
Grant a custom badge through the API Integrations rest-api , how-to	9	8143	18. November 2023
Improved badge granting workflow Feature badges , completed	29	5331	23. Januar 2018
Wishlist: visual cue for "user got a badge for this post" Feature badges	36	2296	5. Dezember 2024
Bulk Award a badge to a set of users Announcements badges , new-feature	28	6632	31. März 2025

Können Benutzernamen im Webhook-Payload von user_badge enthalten werden?

Verwandte Themen