# Get the legitimate interests assessment

> GET /v1/compliance/lia. The published LIA (EM-LIA-2026-03) with its version history.

Source: https://emailmovers.com/mydatahub/docs/reference/rest/get-lia

`GET /v1/compliance/lia`

The published LIA (EM-LIA-2026-03) with its version history.

| Property | Value |
| --- | --- |
| Endpoint | `GET https://mydatahub.emailmovers.com/v1/compliance/lia` |
| Operation id | `getLia` |
| Cost | Free (0 credits) |
| Access | No account, key or token needed. |
| Tag | Compliance |

> **Not yet live.** MyDataHub v2 is built and tested locally and is not yet live. The v2 hosts open at launch, date to confirm. This page describes the contract the API is tested against.

## Request

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `MyDataHub-Version` | header | string | no | The dated API version, pinned per key when left out. Non-breaking changes ship as new dates; the path major changes only for breaking changes, with a 12 month deprecation window. |

## Example request

```bash
curl "https://mydatahub.emailmovers.com/v1/compliance/lia"
```

## Responses

### 200: The LIA.

Headers: `RateLimit`, `RateLimit-Policy`.

| Member | Type | Always present | Description |
| --- | --- | --- | --- |
| `ref` | string | yes |  |
| `version` | string | yes |  |
| `published_at` | string (date) | yes |  |
| `url` | string (uri) | yes |  |
| `lawful_basis` | enum: `legitimate_interests_art6_1_f` | yes |  |
| `summary` | string | yes |  |
| `versions` | array of object | yes |  |
| `versions[].ref` | string | yes |  |
| `versions[].published_at` | string (date) | yes |  |
| `versions[].url` | string (uri) | yes |  |

#### Example response

```json
{
  "ref": "EM-LIA-2026-03",
  "version": "2026-03",
  "published_at": "2026-11-30",
  "url": "https://emailmovers.com/trust/lia",
  "lawful_basis": "legitimate_interests_art6_1_f",
  "summary": "Emailmovers relies on UK GDPR Article 6(1)(f) legitimate interests for named business contacts, with direct marketing as an Article 6(1)(f) example since 5 February 2026.",
  "versions": [
    {
      "ref": "EM-LIA-2026-03",
      "published_at": "2026-11-30",
      "url": "https://emailmovers.com/trust/lia"
    }
  ]
}
```

## Errors

Every error is a problem object with a `code` and a `next_step`. Every response carries the `RateLimit` and `RateLimit-Policy` headers; see [Rate limits](https://emailmovers.com/mydatahub/docs/rate-limits.md).

| Status | Problem codes | When |
| --- | --- | --- |
| 400 | [`invalid-request`](https://emailmovers.com/mydatahub/docs/errors/invalid-request.md), [`idempotency-key-required`](https://emailmovers.com/mydatahub/docs/errors/idempotency-key-required.md), [`unsupported-version`](https://emailmovers.com/mydatahub/docs/errors/unsupported-version.md) | The request could not be read, or an Idempotency-Key is missing. |
| 429 | [`rate-limited`](https://emailmovers.com/mydatahub/docs/errors/rate-limited.md) | Too many requests. Wait for Retry-After. |
| Any other failure | [`internal-error`](https://emailmovers.com/mydatahub/docs/errors/internal-error.md), [`service-unavailable`](https://emailmovers.com/mydatahub/docs/errors/service-unavailable.md), [`tps-screen-expired`](https://emailmovers.com/mydatahub/docs/errors/tps-screen-expired.md) | Something failed on our side (500 internal-error) or the service is briefly unavailable (503 service-unavailable, with Retry-After). Nothing was charged; retry with the same Idempotency-Key. A count, sample, quote or order with telephone in play is also refused with 503 tps-screen-expired, with no Retry-After, while the dataset version's TPS and CTPS screen is more than 28 days old. |