---
title: "Create Namespace Snapshot"
method: POST
path: "/v1/namespaces/{namespace_identifier}/snapshots"
tags: ["Namespace Snapshots"]
---

# Create Namespace Snapshot

`POST /v1/namespaces/{namespace_identifier}/snapshots`

Create a point-in-time snapshot of the entire namespace. Captures all MongoDB documents and an S3 object manifest. Optionally copies S3 objects to the snapshot prefix for full data preservation (required if you plan to delete the namespace and restore later).

## Path parameters

- `namespace_identifier` string, required — Namespace name or ID

## Request body

- CreateSnapshotRequest
  - `copy_s3_objects` boolean — If true, S3 objects are copied to the snapshot prefix (slower, uses more storage). Required for restoring after namespace deletion.
  - `include_vectors` boolean — If false, creates a METADATA-ONLY snapshot (no vector export). Advanced — on restore the vectors are stitched from the shard representative's export (see MI-894). Daily sweeps use this to coalesce the full-dataset vector export to one per physical shard.

## Response `200`

Successful Response

- CreateSnapshotResponse
  - `task_id` string, required
  - `snapshot_id` string, required
  - `message` string, required

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `422` — Validation Error
- `500` — Internal Server Error

---

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