Encode interaction information such as command name in the URL of POST requests to application interaction endpoint URL

[ghost]

So I mentioned this in the discord-api discord and they suggested posting it here...

So right now Discord simply POSTs to the exact same interactions endpoint URL you provide, and all information is in the JSON body. I think it would be a good idea if Discord were to append REST-style information to that URL, for example, POST {interaction_url}/commands/examplecommand when someone uses /examplecommand. This has the following advantages:

1. It will make it nicer and more straight-forward to develop apps with your favorite http framework, as commands and such can be defined as HTTP endpoints:

// express.js
app.post("/commands/example", (req, res) => {
    // request already verified and req.body parsed as json by middleware
    res.send({type: 4, data: {content: "ayy"} }); // convenience methods could be added by middleware for this
});

2. It would enable flexibility with HTTP routing. A reverse proxy could route commands to completely separate programs:

# caddy
my-cool-app.com {
    reverse_proxy /commands/a localhost:1234
    reverse_proxy /commands/b localhost:2345
}

[ckohen]

I love this, but how does it apply to the gateway? Is it an outgoing webhook only option that discord has to develop strictly for that use case?

[ghost]

Gateway is not relevant, this is just about the way discord sends "outgoing webhooks".

[ckohen]

It is though. They are clearly worried about consistency between the gateway and outgoing webhooks. Like I said, I love this, but I'm trying to figure out what incentivizes Discord to actually implement it.

[ghost]

um, gateway doesn't involve http urls; there is no way this can apply to the gateway.

The payloads would still be exactly the same but this is about something that the gateway doesn't have, outside of the payload.

[ckohen]

Right, that's my point. In the past they've said we can't get the message in the response when responding via the gateway because HTTP bots wouldn't get the same (can't respond to a response). So this being an HTTP only thing breaks that consistency.

Also worth mentioning, you'd need to include more than just the name if this was implemented