---
title: "Enabling Project Managed Encryption"
method: POST
path: "/v1/projects/{id}/key"
tags: ["Projects"]
---

# Enabling Project Managed Encryption

`POST /v1/projects/{id}/key`

_(introduced: version 0.6)_

[Project Managed Encryption](/central-api-encryption) can be enabled via the API. To do this, `POST` with the `passphrase` and optionally a reminder `hint` about the passphrase. If managed encryption is already enabled, a `409` error response will be returned.

Enabling managed encryption will modify all unencrypted forms in the project, and as a result the `version` of all forms within the project will also be modified. It is therefore best to enable managed encryption before devices are in the field. Any forms in the project that already have self-supplied encryption keys will be left alone.

## Path parameters

- `id` number, required

## Response `200`

OK

- object
  - `id` number — The numerical ID of the Project.
  - `name` string, required — The name of the Project.
  - `description` string — The description of the Project, which is rendered as Markdown on Frontend.
  - `keyId` number — If managed encryption is enabled on the project, the numeric ID of the encryption key as tracked by Central is given here.
  - `archived` boolean — Whether the Project is archived or not. `null` is equivalent to `false`. All this does is sort the Project to the bottom of the list and disable management features in the web management application.

## Other responses

- `400` — Bad Request
- `409` — Conflict

---

[API](https://skmtc.net/getodk/apis/odk-central-api.md) · [All operations](https://skmtc.net/getodk/apis/odk-central-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/getodk/odk-central-api/versions/d8f5a0886a8b/schema)