# Email domain endpoints are being retired

**Sunset date:** 2027-01-31
**Reason for the change:** automatic joining of a company by email domain has been withdrawn, so the company email-domain endpoints have no replacement.

:::warning

The four routes below will stop working from the start of **2027-01-31** (00:00 UTC, the instant in the `Sunset` header). They have no `v2/` replacement: remove any call to them from your integration before this date.

:::

## What changed

| Route | Behaviour now |
|---|---|
| `GET /api/company/{companyId}/email-domains` | Still works and returns the existing registrations. Sends `Deprecation` and `Sunset` response headers. |
| `POST /api/company/{companyId}/email-domains` | Always returns `410 Gone`. |
| `DELETE /api/company/{companyId}/email-domains/{domainId}` | Always returns `410 Gone`. |
| `POST /api/company/{companyId}/email-domains/{domainId}/restore` | Always returns `410 Gone`. |

The write routes have returned `410 Gone` since the withdrawal; this notice puts a sunset date on all four so their removal follows the [API Versioning Policy](/api-versioning-policy).

## Checklist for migrating

- [ ] Stop calling the four routes above.
- [ ] Remove any handling that expects a registered email domain to add people to a company automatically.

## Related

- [API Versioning Policy](/api-versioning-policy)
- [API Changelog](/api-changelog)