Get the target users for an invite in Discord
A documented Discord operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get the target users for an invite.
- GETReads data
discord.com/invites/{code}/target-users
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Discord operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Discord operations
- Update the target users for an existing invitePUT · changes data
- Set a voice channel's statusPUT · changes data
- Create an exception to a recurring guild scheduled eventPOST · changes data
- Update the external moderation metadata for a lobby messagePUT · changes data
- Deletes the specified lobby if it existsDELETE · changes data
- Update the external moderation metadata for a user message (DM)PUT · changes data
- Modifies the incident actions of the guildPUT · changes data
- Delete an exception to a recurring guild scheduled eventDELETE · changes data
Questions
- Can HumDay get the target users for an invite in Discord?
- Yes. This operation is published in Discord's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Discord account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Discord.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Discord account.
Where this came from
Read from the API description Discord publishes themselves at raw.githubusercontent.com/discord/discord-api-spec/main/specs/openapi.json. The description above is the provider’s own wording, not ours.