Delete an empty folder

DELETE/api/v1/mailbox/folders/{folder}

Requires amailbox token— it acts as one mailbox holder, not as the organization.

folder is the id GET /folders returns. Refused with 409 cannot_delete_special_folder for INBOX and the special-use folders, and with 409 folder_not_empty (messages) or folder_has_subfolders while anything is still inside -- IMAP DELETE destroys contents without a Trash step, so the holder empties the folder deliberately first. The client should warn on 409 rather than retry.

Parameters

Name	In	Type	Description
`folder`required	path	string

Request

DELETE/api/v1/mailbox/folders/{folder}

curl -X DELETE 'https://app.mailyte.com/api/v1/mailbox/folders/01JBT8XQ2M9WYC3K4F6R7S8T9V' \
  -H 'Authorization: Bearer MAILBOX_TOKEN'

const response = await fetch('https://app.mailyte.com/api/v1/mailbox/folders/01JBT8XQ2M9WYC3K4F6R7S8T9V', {
  method: 'DELETE',
  headers: {
    Authorization: 'Bearer MAILBOX_TOKEN',
  },
});
const { data } = await response.json();

import requests
response = requests.delete(
    "https://app.mailyte.com/api/v1/mailbox/folders/01JBT8XQ2M9WYC3K4F6R7S8T9V",
    headers={"Authorization": "Bearer MAILBOX_TOKEN"},
)
data = response.json()["data"]

<?php

$response = Http::withToken('MAILBOX_TOKEN')
    ->delete('https://app.mailyte.com/api/v1/mailbox/folders/01JBT8XQ2M9WYC3K4F6R7S8T9V');

$data = $response->json('data');

require "net/http"
require "json"
uri = URI("https://app.mailyte.com/api/v1/mailbox/folders/01JBT8XQ2M9WYC3K4F6R7S8T9V")
request = Net::HTTP::Delete.new(uri)
request["Authorization"] = "Bearer MAILBOX_TOKEN"
response = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |http| http.request(request) }

The key names its own organization, so no X-Organization-ID header is needed.

Response

Successful Response

Returned inside the standard envelope.

Errors

Status	When
`422`	Validation Error

Every status, with what causes it and what to do, is on the error reference.