application_delete

Remove a join application from the record. Moderators use it to clear old applications. A member can also use it to withdraw their own pending application.

Request

{
  "cmd": "application_delete",
  "application_id": "5b1f3c1e-8d0a-4d6e-9f43-2a7c9e1b0d55"
}

Field	Type	Required	Description
`application_id`	string	With `manage_access`	The application to delete. Without `manage_access`, it defaults to your own pending application, and any other ID is refused.

Response

{
  "cmd": "application_delete",
  "application_id": "5b1f3c1e-8d0a-4d6e-9f43-2a7c9e1b0d55",
  "deleted": true
}

The deletion is recorded in the audit log. Nobody else is notified.

Deleting an application doesn’t undo its review. An approved applicant stays on the whitelist; remove them with whitelist_remove.

Permissions

With manage_access, you can delete any application, in any status.
Without it, you can delete only your own pending application.

The caller must be an authenticated member, so an applicant who hasn’t been admitted can’t withdraw. review_applications alone doesn’t allow deleting other people’s applications. A user in timeout gets a rate_limit frame instead.

Errors

`val`	When
`application_id is required`	The caller has `manage_access` and didn’t send `application_id`.
`Application not found`	No application has that ID, or the server couldn’t save the change.
`Access denied: 'manage_access' permission required`	The caller lacks `manage_access` and either has no pending application or named a different one.

An empty application_id returns the schema validator’s message.

See also