Enable way to see Message ID of interaction source and response #2410

SpencerSharkey · 2020-12-23T10:52:48Z

Description

After acknowledging a slash command interaction, there appears to be no way to get the channel message id for the interaction source message (if you decide to show it), or the message you reply with in the initial response.

Why This is Needed

I think it's important to be able to link an interaction to the messages it sends in a channel. An example could be deleting messages related to the command run after X amount of time to clean up the channel, or to link reactions, replies, etc up to the original messages sent.

Alternatives Considered

A way to hide the interaction source message after acknowledging it, which may be enough for most folks.
Including an interaction ID on the message objects (painful to sync these events w/ interaction flows)

Additional Details

I know this wouldn't be too useful if your application doesn't have a bot user- but for the ones that do the extra control would be appreciated. It looks like you can hack something together by comparing a message's content (</slash:12312312312> <args>) and type against the interactions your app provides, but it would be a lot of extra work for something that could be provided w/ the interaction API.

The text was updated successfully, but these errors were encountered:

msciotti · 2021-01-06T00:19:34Z

Definitely valid. A little tricky from an API ergonomics perspective--you respond to an interaction by issuing an HTTP response code, so we can't like...respond to your response 😄

We could perhaps allow you to GET /@original much like you can EDIT and DELETE. It would be an extra step but maybe an OK enough short term fix?

ckohen · 2021-01-06T00:22:31Z

Maybe if the response is sent to the /callback endpoint you can respond to that with the message ID, and provide that GET /@original endpoint for the REST only applications

msciotti · 2021-01-15T19:59:25Z

We're going to support this by making the GET /@original endpoint. It definitely is less ergonomic for gateway connections--which sucks, I apologize--but it's an easy way to support both methods with the same code.

EDIT: I realized that addressed half the issue. As for getting the ID of the source message, we have some thoughts there about how design changes may impact the relationship between source and responses, so no update on the source message id yet as we figure that out.

SpencerSharkey · 2021-01-16T11:15:33Z

If the GET ../@original returns the full message object, that sounds great.

msciotti · 2021-01-19T17:29:56Z

It should. You can technically mock this behavior today by sending an empty PATCH ../@original :p

msciotti · 2021-03-03T19:12:07Z

So, with some changes to messages and interactions in #2615, this "source message" concept is going away. And, some interaction metadata is sent on the message object that you'd receive in a message create.

So, you could:

Receive an interaction
Respond to it, noting it's unique id
Listen for MESSAGE_CREATE events on the gateway with the matching ID

Since deleting the original source message isn't a thing (they're now all one message), is a GET endpoint still needed, or does this new metadata help?

ckohen · 2021-03-03T19:53:28Z

Would that mean that the interaction id received with the INTERACTION_CREATE payload is now the same as the message id of the response message? Or am I misunderstanding that.

Also, I still believe the GET endpoint would be necessary, as you will get the message object when using type 5 inherently by using the PATCH endpoint to finish your response, but when responding directly, there's no way to achieve this without a bot.

I also assume PATCH would no longer work after the 15 minute expiry period, whereas GET might? I generally think more from a gateway perspective, so this wouldn't really affect me personally, but there might be some use for those only using HTTP.

A5rocks · 2021-03-03T20:10:00Z

Would that mean that the interaction id received with the INTERACTION_CREATE payload is now the same as the message id of the response message? Or am I misunderstanding that.

I believe Mason is referring to ddc0d13.

ckohen · 2021-03-03T20:14:44Z

Ah, I missed that commit 🤦. I still believe the rest of points are valid though.

TorKallon · 2021-03-23T18:23:50Z

Any news on this? Will there still be a GET method or will watching for the message in the event stream be the only way to get the message ID?

Skillz4Killz · 2021-03-23T18:50:07Z

Quick hackish workaround:

You can use the interaction webhook token as a normal webhook execution with ?wait=true and get the message id from that.

msciotti · 2021-04-09T01:02:07Z

Update on this: we had a PR that got merged, then reverted due to some failing tests.

We'll be adding:

/webhooks/<webhook_id>/<webhook_token>/messages/@original
/webhooks/<webhook_id>/<webhook_token>/messages/<message_id>

And will document them when they're merged!

ThaTiemsz · 2021-04-14T01:04:20Z

Update on this: we had a PR that got merged, then reverted due to some failing tests.

We'll be adding:
/webhooks/<webhook_id>/<webhook_token>/messages/@original
/webhooks/<webhook_id>/<webhook_token>/messages/<message_id>
And will document them when they're merged!

These endpoints are live now

BREAKING CHANGE: possibly a breaking change due to the fact that the messageID is now strictly typed as a Snowflake or `@me` - Reference: discord/discord-api-docs#2410

qaisjp · 2021-04-14T22:51:18Z

This is great news. Will this pave some road for #2251?

RedDaedalus · 2021-04-14T22:52:16Z

Discord has said multiple times that webhooks replying to messages will never happen. Allowing replies would let webhooks access any message but this behavior only lets them access their own (which they could theoretically access anyway by caching sent messages).

qaisjp · 2021-04-14T22:56:13Z

My implication here is that replies could be possible for replying to own webhook-created messages.

I'm aware of one engineer's immediate feedback that this is not going to happen right now. Considering the fact that #2251 is still open, I am hopeful that this is not a "will never happen" situation.

night · 2021-04-19T20:20:49Z

Closing this since the endpoint is live

SpencerSharkey added the slash commands label Dec 23, 2020

typpo added the api API issue label Dec 23, 2020

discord deleted a comment from drzheer Jan 6, 2021

msciotti added the synced Synced to internal tracker label Jan 6, 2021

msciotti added the planned We're going to fix this pretty soon label Jan 15, 2021

msciotti mentioned this issue Jan 15, 2021

Slash Command Feedback Master List #2490

Closed

20 tasks

ckohen mentioned this issue Feb 17, 2021

Changes to interaction responses and flags #2615

Merged

Snazzah mentioned this issue Apr 9, 2021

GET Messages of the original interaction message Snazzah/slash-create#47

Closed

night assigned typpo Apr 9, 2021

night added the feature request label Apr 9, 2021

JohnnyJayJay mentioned this issue Apr 12, 2021

Implement slash command and new webhook endpoints discljord/discljord#64

Merged

5 tasks

vladfrangu mentioned this issue Apr 14, 2021

docs(Routes): add GET route to webhookMessage discordjs/discord-api-types#114

Merged

This was referenced Apr 14, 2021

feat(Webhook): add 'fetchMessage' method discordjs/discord.js#5530

Merged

Document Get Webhook Message / Original Interaction Response #2812

Merged

qaisjp mentioned this issue Apr 14, 2021

Allow webhooks to use reply messages #2251

Closed

night closed this as completed Apr 19, 2021

ASarrouj mentioned this issue May 22, 2021

Add missing message methods to interaction response #2980

Closed

SpencerSharkey mentioned this issue Jun 21, 2021

Provide interaction response message data when using /callback #3153

Closed

braindigitalis mentioned this issue Jul 20, 2021

Finished implementing editing of slash command interaction responses brainboxdotcc/DPP#46

Merged

42wim mentioned this issue Feb 5, 2022

Linking Slack threads to Discord threads 42wim/matterbridge#1558

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Enable way to see Message ID of interaction source and response #2410

Enable way to see Message ID of interaction source and response #2410

SpencerSharkey commented Dec 23, 2020 •

edited

Loading

msciotti commented Jan 6, 2021

ckohen commented Jan 6, 2021

msciotti commented Jan 15, 2021 •

edited

Loading

SpencerSharkey commented Jan 16, 2021

msciotti commented Jan 19, 2021

msciotti commented Mar 3, 2021

ckohen commented Mar 3, 2021

A5rocks commented Mar 3, 2021

ckohen commented Mar 3, 2021

TorKallon commented Mar 23, 2021

Skillz4Killz commented Mar 23, 2021

msciotti commented Apr 9, 2021

ThaTiemsz commented Apr 14, 2021

qaisjp commented Apr 14, 2021

RedDaedalus commented Apr 14, 2021 •

edited

Loading

qaisjp commented Apr 14, 2021 •

edited

Loading

night commented Apr 19, 2021

Enable way to see Message ID of interaction source and response #2410

Enable way to see Message ID of interaction source and response #2410

Comments

SpencerSharkey commented Dec 23, 2020 • edited Loading

msciotti commented Jan 6, 2021

ckohen commented Jan 6, 2021

msciotti commented Jan 15, 2021 • edited Loading

SpencerSharkey commented Jan 16, 2021

msciotti commented Jan 19, 2021

msciotti commented Mar 3, 2021

ckohen commented Mar 3, 2021

A5rocks commented Mar 3, 2021

ckohen commented Mar 3, 2021

TorKallon commented Mar 23, 2021

Skillz4Killz commented Mar 23, 2021

msciotti commented Apr 9, 2021

ThaTiemsz commented Apr 14, 2021

qaisjp commented Apr 14, 2021

RedDaedalus commented Apr 14, 2021 • edited Loading

qaisjp commented Apr 14, 2021 • edited Loading

night commented Apr 19, 2021

SpencerSharkey commented Dec 23, 2020 •

edited

Loading

msciotti commented Jan 15, 2021 •

edited

Loading

RedDaedalus commented Apr 14, 2021 •

edited

Loading

qaisjp commented Apr 14, 2021 •

edited

Loading