API Reference / Endpoints
Delete Subscriber
The Delete Subscriber endpoint removes a subscriber from your waitlist by either their unique ID or email address. It's the counterpart to Add Subscriber — useful for GDPR removal requests and cleaning up test data.
Deletion runs through the same pipeline as the dashboard: the subscriber (and their email history) is removed, analytics counters are decremented, and queue positions are compacted. This happens asynchronously — expect counters and positions to update within a few minutes.
Want the full picture in one fetch? The one-page integration guide covers every path with copy-paste code · OpenAPI spec · SDK: npm install waitlister
Endpoint Details
- URL:
https://waitlister.me/api/v1/waitlist/{waitlist-key}/subscribers/{id-or-email} - Method:
DELETE
Request
Headers
X-Api-Key: your-api-key
Path Parameters
| Parameter | Description |
|---|---|
waitlist-key | Your unique waitlist key, found in your waitlist settings |
id-or-email | Either the subscriber's unique ID or their email address |
Example Request
curl -X DELETE "https://waitlister.me/api/v1/waitlist/your-waitlist-key/subscribers/user@example.com" \
-H "X-Api-Key: your-api-key"
Response
Success Response 200
{
"success": true,
"message": "Subscriber deleted. Analytics and positions will update shortly."
}
Error Responses
| Status Code | Description |
|---|---|
400 | Missing subscriber ID or email |
401 | Invalid API key or waitlist key |
403 | Your plan doesn't include this endpoint, or the subscriber belongs to another waitlist |
404 | Subscriber not found |
429 | Rate limit exceeded |
Notes
- Deletion is permanent — the subscriber's data, points, and referral history cannot be restored.
- If the subscriber referred others, referral-derived points are recalculated by the same process the dashboard uses.
- The subscriber may still appear in List Subscribers for a few seconds after the request returns, until asynchronous processing completes.
