# Delete lost card record

`DELETE /api/configuration/lost-cards/{all}`

- **Products:** Operator (`FOH`)
- **Features:** Front of House Generic Access (`FOHGENERIC`)

HTML version: [Delete lost card record](https://support.gladstonesoftware.cloud/reference/configuration/delete-lost-card-record)

## Overview

Removes an entry from the lost cards register. Where the entry's identifier is a card number, that card is no longer blocked from reuse. This is a hard delete: the record is removed outright. There is no deleted or inactive flag on a lost card record, so there is nothing to reverse and no deactivate alternative. An entry deleted in error cannot be recreated as it was: [Create lost card record](create-lost-card-record.md) makes a new entry with a new generated identifier and no card number.

There is no separate existence check. If the id does not match a lost card record, the response is `404` with an empty body, so a repeat of the same request returns `404` rather than succeeding silently.

A successful call returns `204 No Content` with no body, and subsequent reads of the lost card list reflect the deletion.

The path segment shown as `{all}` is the lost card id, not a literal.

## Endpoint

`DELETE {base_url}/api/configuration/lost-cards/{all}`

`{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 |
|------|------|----------|-------------|
| `lostCardId` | string | Yes | The entry's `id` as returned by [Get all lost cards](get-all-lost-cards.md): a card number, or a generated upper-case GUID for entries created through [Create lost card record](create-lost-card-record.md). It is unique within your tenant. |

## Sample request

```bash title="cURL"
curl -X DELETE '{base_url}/api/configuration/lost-cards/{all}' \
  -H 'Authorization: Bearer {accessToken}' \
  -H 'X-Use-SSO: true'
```

## Errors

| Status | Meaning | When |
|--------|---------|------|
| `400` | Bad request | The id is empty — `Id cannot be null or empty`. In practice a request with an empty segment does not reach this endpoint, so you will rarely see this. |
| `404` | Not found | No lost card record exists with that id. The body is empty — unlike most `404`s on this API, no message is returned. A repeated delete of the same card gives the same result. |
| `409` | Conflict | Another record references this lost card and blocks the delete — `There are records linked to the ID {lostCardId} that are stopping the operation being completed`. |
| `500` | Internal server error | The delete failed for any other reason. Nothing is deleted, and the request is safe to retry. |