# Delete emergency contact record

`DELETE /api/members/emergency-contacts/{id}`

- **Products:** Operator (`FOH`), Consumer (`CONSUMER`) (any one of these products, not all)
- **Features:** Online Joining (`ONLINEJOIN`), Front of House Generic Access (`FOHGENERIC`) (any one of these features, not all)

HTML version: [Delete emergency contact record](https://support.gladstonesoftware.cloud/reference/members/delete-emergency-contact-record)

## Overview

Removes one emergency contact — the counterpart to
[Create emergency contact for member](create-emergency-contact-for-member.md).
Use it when a member withdraws a contact, when a duplicate was created, or when you are replacing
a contact outright rather than editing it with
[Update emergency contact record](update-emergency-contact-record.md). On success
you get `204 No Content` with no body, and only the contact you named is removed — the member's
other contacts are untouched.

The deletion is permanent: the contact is removed rather than flagged as deleted, so
there is nothing to restore and no undo. Deleting the same id a second time returns `404` with an
empty body rather than succeeding quietly, so if you are retrying after a timeout, treat that
`404` as "already done".

The path takes the **contact record's own id**, not the member id. Read it from
`emergencyContacts[].id` in
[Get member emergency contacts](get-member-emergency-contacts.md). No member id
appears anywhere in this route, and that has a consequence worth planning for: unlike creating a
contact, this endpoint performs **no check that the record belongs to the caller**. Any caller
holding a valid token for the tenant can delete any emergency contact in that tenant, including
another member's, provided they know or guess its id. If you expose deletion to end users, enforce
ownership yourself — list the member's own contacts first, and only delete ids that came back in
that response.

There is no bulk form of this call. To clear a member's contacts, list them and delete them one at
a time.

## Endpoint

`DELETE {base_url}/api/members/emergency-contacts/{id}`

`{base_url}` is the environment URL issued to your integration. See [Authenticating with Gladstone APIs](../../guides/authenticating-with-gladstone-apis.md).

## Path parameters

| Name | Type | Required | Description |
|------|------|----------|-------------|
| `id` | integer (int32) | Yes | The emergency contact record to remove, as `emergencyContacts[].id` from [Get member emergency contacts](get-member-emergency-contacts.md). This is the contact's own id, not the member id — both are plain integers, so sending a member id by mistake is not rejected as malformed: it either deletes whichever contact happens to carry that id, or returns `404`. |

## Sample request

```bash title="cURL"
curl -X DELETE '{base_url}/api/members/emergency-contacts/{id}' \
  -H 'Authorization: Bearer {accessToken}' \
  -H 'X-Use-SSO: true'
```

## Errors

| Status | Meaning | When |
|--------|---------|------|
| `404` | Not found | No emergency contact has that id — either it never existed, or a previous delete already removed it. The response body is empty. |
| `500` | Internal server error | An unexpected server-side failure. The response has no body, and the contact may or may not have been removed — re-read the member's contacts with [Get member emergency contacts](get-member-emergency-contacts.md) rather than assuming. |