Skip to content

Sender Identity API - Delete

Use this endpoint to delete a sender identity from your account.


DELETE https://e1.envoke.com/v1/senders/{ID}

Replace {ID} with the Envoke sender ID you want to delete. Authentication is via HTTP Basic Auth using your API ID and API Key.


Deletion is permanent. Deleted sender identities cannot be recovered via the API.

The default sender cannot be deleted. If you need to remove the current default, first use POST /v1/senders/{ID}/default to promote a different identity as the default, then delete the former default.


On success:

{
"success": true,
"result_text": "Deleted",
"result_data": []
}

If the sender ID is not found:

{
"success": false,
"result_text": "Validation failed, see 'result_data' -> 'errors'",
"result_data": {
"errors": ["Item with id '42' not found"]
}
}

If you attempt to delete the default sender:

{
"success": false,
"result_text": "Validation failed, see 'result_data' -> 'errors'",
"result_data": {
"errors": ["The default sender identity cannot be deleted"]
}
}

Terminal window
curl -X DELETE -gs \
-u "$API_ID:$API_KEY" \
"$BASE/v1/senders/4"

Promote a new default, then delete the old one

Section titled “Promote a new default, then delete the old one”

If you need to delete the current default, promote another sender first:

Terminal window
# Step 1 — promote sender 2 as the new default
curl -X POST -gs \
-u "$API_ID:$API_KEY" \
"$BASE/v1/senders/2/default"
# Step 2 — delete the old default (sender 1)
curl -X DELETE -gs \
-u "$API_ID:$API_KEY" \
"$BASE/v1/senders/1"

Note: The curl examples above are formatted for readability. All requests must use properly encoded URLs.

Full reference, OpenAPI description, and Postman collection: developers.envoke.com.