Reference

Get the legitimate interests assessment

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

Generated from the contractsView as Markdown

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

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

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

Responses

200: The LIA.

Headers: RateLimit, RateLimit-Policy.

Member	Type	Always present
`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

{
  "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.

Status	Problem codes	When
400	`invalid-request`, `idempotency-key-required`, `unsupported-version`	The request could not be read, or an Idempotency-Key is missing.
429	`rate-limited`	Too many requests. Wait for Retry-After.
Any other failure	`internal-error`, `service-unavailable`, `tps-screen-expired`	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.