gorb/backend

Fork 0

Change ban endpoint #46

New issue

Open

opened 2025-08-07 05:13:26 +00:00 by sauceyred · 2 comments

sauceyred commented

2025-08-07 05:13:26 +00:00

Owner

I think that instead of doing:
POST /members/{id}/ban

{
  "reason": "..."
}

It would make more sense for it to be:
POST /guilds/{id}/bans

{
  "member_id": "...",
  "reason": "..."
}

Thoughts?

I think that instead of doing: `POST /members/{id}/ban` ```json { "reason": "..." } ``` It would make more sense for it to be: `POST /guilds/{id}/bans` ```json { "member_id": "...", "reason": "..." } ``` Thoughts?

radical commented

2025-08-07 05:34:08 +00:00

Owner

I think we should re-rework our endpoints, thoughts?

baaboe commented

2025-08-12 12:10:23 +00:00

Member

Should we then just remove the entire member endpoint and, only use the guild endpoint?

No labels

No milestone

No project

No assignees

3 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: gorb/backend#46

No description provided.

Rows
Columns