Edit history

Earlier versions of Add owner information to /applications/@me endpoint, newest first.

Current version | Edited by Rex
Changes
https://docs.discord.com/developers/resources/application#application-objectRemoved: ### ChecksRemoved: Removed: - ☑ I searched for existing discussions and didn't find a duplicate.Removed:
Show

Add owner information to /applications/@me endpoint

Problem

I'm trying to get information about the owner of the application from my bot so that I can automatically know, who should have access to the bot owner commands.

Proposed solution

Add an owner key with partial user info to the application object returned by /applications/@me endpoint, similarly to what Discord does: https://docs.discord.com/developers/resources/application#application-object
Edited by Rex
Changes
https://docs.discord.com/developers/resources/application#application-objectRemoved: ### Notes (optional)Removed: Removed: _No response_Removed: ### Checks
Show

Add owner information to /applications/@me endpoint

Problem

I'm trying to get information about the owner of the application from my bot so that I can automatically know, who should have access to the bot owner commands.

Proposed solution

Add an owner key with partial user info to the application object returned by /applications/@me endpoint, similarly to what Discord does: https://docs.discord.com/developers/resources/application#application-object

Checks

  • ☑ I searched for existing discussions and didn't find a duplicate.
Original by Rex
Show

Add owner information to /applications/@me endpoint

Problem

I'm trying to get information about the owner of the application from my bot so that I can automatically know, who should have access to the bot owner commands.

Proposed solution

Add an owner key with partial user info to the application object returned by /applications/@me endpoint, similarly to what Discord does: https://docs.discord.com/developers/resources/application#application-object

Notes (optional)

No response

Checks

  • ☑ I searched for existing discussions and didn't find a duplicate.