---
title: "Update a provisioned domain (toggle historical backfill)"
method: PATCH
path: "/v1/provisioned-domains/{provisioned_id}"
tags: ["provisioned-domains"]
---

# Update a provisioned domain (toggle historical backfill)

`PATCH /v1/provisioned-domains/{provisioned_id}`

## Request

- Base URL: `https://api.ctindex.io`
- URL: `https://api.ctindex.io/v1/provisioned-domains/{provisioned_id}`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Toggles the paid per-domain deep-historical (expired / deep-past) certificate backfill entitlement for a provisioned domain owned by the caller. The flag is off by default; enabling it lets the caller trigger a full-history walk for this domain via the backfill API / MCP tool. Active-cert lookups are unaffected and remain free.

## Path parameters

- `provisioned_id` string, uuid, required

## Cookies

- `ctix_session` string, nullable

## Request body

- ProvisionedDomainUpdate: Body for ``PATCH /v1/provisioned-domains/{provisioned_id}``. Task #256 — toggles the per-domain deep-historical backfill entitlement. The field is optional so the PATCH can no-op (or later carry other mutable fields) without forcing the caller to resend the flag.
  - `historical_backfill_enabled` boolean, nullable

## Response `200`

Successful Response

- ProvisionedDomainEntry: One row in ``GET /v1/provisioned-domains``.
  - `id` string, uuid, required
  - `domain` string, required
  - `status` string, required
  - `monthly_cost_usd` integer
  - `stripe_subscription_item_id` string, nullable
  - `created_at` string, date-time, nullable
  - `historical_backfill_enabled` boolean

## Other responses

- `422`: Validation Error

---

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