In JDA 3.x, we now specify all Discord Routes. These are the routes left to be added.
Class can be seen here: link
Thanks to @MinnDevelopment for writing up this list.
Base: https://discordapp.com/api/
Global Endpoints
Bot Only
Client Only
guilds GET
should be
users/@me/guilds GET
guilds/:guild_id/channels/:channel_id PATCH Does not exist based on API docs. Does it actually exist?
added guilds/:guild_id/channels PATCH. This is the batch channel position change endpoint.
RE: guilds/:guild_id/channels/:channel_id PATCH
Does not exist, I checked and it was 404.
guilds/:guild_id/invites POST
POST is not allowed for this endpoint. Use channels/:channel_id/invites POST instead.
Missing endpoint: guilds/:guild_id/integrations GET
So guilds/:guild_id/invites POST effectively does not exist, yes? That means that you can only create invites with channels/:channel_id/invites POST right?
guilds/:guild_id/invites exists but the only allowed method is GET.
POST returned status 405: Method not allowed
Creating an invite is only possible through the channels endpoint.
guilds/:guild_id DELETE is not used to delete a guild.
It is used to leave a guild.
Reason: 2FA Guild delete requires a code which has to be provided to guilds/:guild_id/delete using POST.
Note: Without 2FA = POST {}
Edit: The one implemented here should not be listed under client only, renamed to LEAVE_GUILD and the correct endpoint is users/@me/guilds/:guild_id DELETE (returns 401 status if owned)
You are missing some bot endpoints probably: https://gist.github.com/SinisterRectus/9518f3e7d0d1ccb4335b2a0d389c30b0
Track endpoint: track POST
It takes a JSON object with the contents:
eventpropertiesType and Source ({Type: "Instant Invite Modal", Source: "Invite Notice"})tokenEmoji endpoints:
guilds/:guild_id/emojis POST //Create emoji
guilds/:guild_id/emojis/:id PATCH //Edit emoji
guilds/:guild_id/emojis/:id DELETE //Remove emoji
POST/PATCH body:
{"name":"abal","roles":["209445206016131073"]}
Note: name is required for POST.
Edit: roles is not available to client accounts anymore, unintended bug.
channel/:channel_id/messages/bulk_delete
should be
channel/:channel_id/messages/bulk-delete
since the former one was deprecated
Also Bulk Delete is listed as PUT here while on discord docs it's POST.
Jake told me that bulk_delete would remain as such for the remainder of gateway v6, only switching when moving to v7, however if bulk-delete works for v6 as well I will switch.
Also, can i get a testing confirmation that it should be POST, not PUT?
No PUT returns status 405 while POST works. (Tested with both unversioned API endpoints)
Edit: Updated the endpoint to POST
We should compare this with the list provided in the official docs #219
I would like to get the rest of these into JDA during the 3.1 development cycle even if we aren't using them yet.
I will cross out any routes that we decide not to include like accepting invites
All routes from this list have now been implemented into JDA.
Can anyone explain how I would go about using this to send a DM to a user?
Go to discord.gg/0hMr4ce0tIl3SLv5 to receive the needed help.