# GET /api/v1/meta-ads/data-deletion/{confirmation_code}

> Meta data deletion status

- **Tag:** meta-ads
- **Operation ID:** `meta_ads_data_deletion_status`

## Description

Public status page for a Meta data deletion request: the link Meta shows the person. Deletion runs before the code is issued, so a valid code always reads as deleted.

## Authentication

Bearer token in `Authorization` header.
Required header: `x-business-id: <business uuid>`.

## Parameters

- `confirmation_code` (path, string, required)

## Responses

### 200 — Successful Response

### 404 — Not Found - Resource does not exist

Schema: `ErrorResponse`

- `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`.
- `message` (string · required) — Human-readable explanation, safe to show to end users.
- `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`).
- `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied.
- `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

### 422 — Validation Error

Schema: `ErrorResponse`

- `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`.
- `message` (string · required) — Human-readable explanation, safe to show to end users.
- `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`).
- `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied.
- `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

## Code samples

### cURL

```bash
curl -X GET 'https://api.ondayzero.com/api/v1/meta-ads/data-deletion/{confirmation_code}' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID'
```

### JavaScript

```javascript
const response = await fetch('https://api.ondayzero.com/api/v1/meta-ads/data-deletion/{confirmation_code}', {
  method: 'GET',
  headers: {
    Authorization: 'Bearer dz_your_token',
    'x-business-id': 'YOUR_BUSINESS_ID',
  },
});
const data = await response.json();
```

### Python

```python
import httpx

headers = {
    "Authorization": "Bearer dz_your_token",
    "x-business-id": "YOUR_BUSINESS_ID",
}

response = httpx.get("https://api.ondayzero.com/api/v1/meta-ads/data-deletion/{confirmation_code}", headers=headers)
data = response.json()
```

## See also

- HTML version: https://www.ondayzero.com/docs/reference/meta-ads/meta-ads-data-deletion-status
- OpenAPI slice: https://www.ondayzero.com/docs/reference/meta-ads/meta-ads-data-deletion-status/openapi.json
- Other endpoints in **meta-ads**: https://www.ondayzero.com/docs/reference/meta-ads (markdown bundle: https://www.ondayzero.com/docs/reference/meta-ads.md, OpenAPI: https://www.ondayzero.com/docs/reference/meta-ads/openapi.json)
- Endpoint catalog: https://www.ondayzero.com/docs/reference/index.md
