Ping interaction fails when using post callbacks option

[fbrettnich]

As soon as the option postCallbacks is set to true, PING requests (Interaction Type 1) for HTTP Interactions can no longer be verified by Discord, as it is currently not possible to respond to PING interactions via the callback endpoint, instead it is required to respond directly to the request with status 200 and PONG (Interaction Callback Type 1) (Docs).

I have already opened a Discord issue (discord/discord-api-docs#7311) for this, but it is unclear if and when this will be changed.

For now, PING interactions should always be answered directly, even if postCallbacks is set to true.

---

2024-12-16 12:48:52  Got request
2024-12-16 12:48:52  Raw Request: Type 1, ID 1318183058574413864, Token aW50ZXJhY3Rpb246MTMx...VElYYnJVd3JrcTdpTmlFcEVZQVkzWQ
2024-12-16 12:48:52  Respond with Status 202
2024-12-16 12:48:52  Raw REST: POST 404 https://discord.com/api/v10/interactions/aW50ZXJhY3Rpb246MTMx...VElYYnJVd3JrcTdpTmlFcEVZQVkzWQ/callback?with_response=true
2024-12-16 12:48:52  POST /interactions/:id/:token/callback (POST:/interactions/:id/:token/callback:global) 404: 153ms | 1/1 left | Reset 1734349732857 (0ms left)

---

slash-create/src/creator.ts

Lines 567 to 585 in a6c1ac7

	if (this.options.postCallbacks && respond)
	await respond({
	status: 202
	});
	if (!respond || !webserverMode || this.options.postCallbacks)
	respond = this._createGatewayRespond(interaction.id, interaction.token);
	switch (interaction.type) {
	case InteractionType.PING: {
	this.emit('debug', 'Ping received');
	this.emit('ping', interaction.user);
	return respond({
	status: 200,
	body: {
	type: InteractionResponseType.PONG
	}
	});
	}

[Snazzah]

Kinda surprised this didn't give me issues in development.

Edit: Discord labeled this as a bug (as it is a valid callback), but since posting pings is pretty unnecessary, I'll change this behavior anyways.