Delete a reply server

DELETE /api/v1/reply-servers/{replyServer}

Performs DELETE on /v1/reply-servers/{replyServer}.

Request

Bearer token required servers.permissions.can_delete_reply_servers

Path parameters

replyServer string required

Responses

All responses are JSON. Errors follow a consistent shape.

200 OK
401 Unauthenticated — missing or invalid API token
404 Not found 
curl -X DELETE "https://getmailpurse.com/api/v1/reply-servers/1" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Accept: application/json"
<?php
$response = \Http::withToken('YOUR_API_TOKEN')
    ->acceptJson()
    ->delete('https://getmailpurse.com/api/v1/reply-servers/1');

$data = $response->json();
const res = await fetch('https://getmailpurse.com/api/v1/reply-servers/1', {
  method: 'DELETE',
  headers: {
    'Authorization': 'Bearer YOUR_API_TOKEN',
    'Accept': 'application/json',
  },
});
const data = await res.json();
import requests

res = requests.request(
    'DELETE',
    'https://getmailpurse.com/api/v1/reply-servers/1',
    headers={
        'Authorization': 'Bearer YOUR_API_TOKEN',
        'Accept': 'application/json',
    },
)
data = res.json()

Try it out

Runs in your browser — nothing is proxied or logged.
This is a DELETE request — it may create, modify or delete real data on your account. 

                    


                    
The request goes straight from your browser to this MailPurse instance. Your token is never sent anywhere else or stored.