const url = 'https://example.com/api/Members/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request DELETE \ --url https://example.com/api/Members/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \ --header 'Authorization: Bearer <token>'Deletes a member. The record is retained internally for history and reporting, but it is gone from this
API: it disappears from the list endpoint and every read of it - this one included - answers 404
afterwards. Deleting is not the same as setting the status to Cancelled, which keeps the member
listed and reinstatable.
The member’s platform account, their transaction history, and subscription and payment data held by the payment gateway are not affected. The same customer can be enrolled again afterwards, which creates a new member.
Deleting does not cancel subscriptions, so it is refused while the member still has any that are not cancelled (409). Cancel them first - otherwise the member would keep being billed while invisible to the staff who deleted them.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The member’s unique identifier.
Responses
Section titled “ Responses ”Member deleted successfully.
No member with the given ID exists, or it has already been deleted.
object
Example generated
{ "type": "example", "title": "example", "status": 1, "detail": "example", "instance": "example"}The member still has subscriptions that are not cancelled.
object
Example generated
{ "type": "example", "title": "example", "status": 1, "detail": "example", "instance": "example"}