---
title: "Meta"
method: GET
path: "/v1/meta"
---

# Meta

`GET /v1/meta`

## Request

- Base URL: `https://api.elaan.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.elaan.io/v1/meta`
- Auth: none declared

Deployment capabilities + build version. Public (like /health): the
console reads it before rendering nav to hide features this profile
doesn't offer.

`registration_open` is the one dynamic capability — a single-tenant
install starts open and closes permanently once its tenant is claimed.
Multi-tenant installs answer it as a constant, without a DB read.

`account_creation_open` mirrors the backend rule that a single-tenant
(on-prem) install is pinned to one account (POST /auth/tenants is 403
there): the console reads it to hide "Create new account".

`data_requests` reports whether we operate this deployment on the
tenant's behalf, and so whether asking us to export or erase their data
means anything. Off on-prem, where they hold the database themselves.

## Response `200`

Successful Response

- object

---

[API](https://skmtc.dev/elaan/apis/elaan-api.md) · [All operations](https://skmtc.dev/elaan/apis/elaan-api/llms.txt) · [OpenAPI document](https://skmtc.dev/elaan/apis/elaan-api/revisions/c96a7e6399aa?raw)