> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mixpeek.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Export Manifest Get

> Export current resources to a YAML manifest.

Exports all resources (or a specific namespace) to a YAML file
that can be version-controlled and re-applied to another environment.

**Features:**
- Resource IDs are converted to human-readable names
- Secret values are replaced with placeholder references (`${{ secrets.NAME }}`)
- Output is formatted for readability and git-friendliness

**Note:** You must configure actual secrets before applying the exported
manifest to a new environment.

**Example:**
```bash
# Export all resources
curl /v1/manifest/export \
  -H "Authorization: Bearer $API_KEY" \
  -o mixpeek.yaml

# Export specific namespace
curl "/v1/manifest/export?namespace_id=ns_abc123" \
  -H "Authorization: Bearer $API_KEY" \
  -o namespace.yaml
```



## OpenAPI

````yaml get /v1/manifest/export
openapi: 3.1.0
info:
  title: Mixpeek API
  description: >-
    This is the Mixpeek API, providing access to various endpoints for data
    processing and retrieval.
  termsOfService: https://mixpeek.com/terms
  contact:
    name: Mixpeek Support
    url: https://mixpeek.com/contact
    email: info@mixpeek.com
  version: '0.82'
servers:
  - url: https://api.mixpeek.com
    description: Production
security: []
paths:
  /v1/manifest/export:
    get:
      tags:
        - Manifest
      summary: Export Manifest Get
      description: >-
        Export current resources to a YAML manifest.


        Exports all resources (or a specific namespace) to a YAML file

        that can be version-controlled and re-applied to another environment.


        **Features:**

        - Resource IDs are converted to human-readable names

        - Secret values are replaced with placeholder references (`${{
        secrets.NAME }}`)

        - Output is formatted for readability and git-friendliness


        **Note:** You must configure actual secrets before applying the exported

        manifest to a new environment.


        **Example:**

        ```bash

        # Export all resources

        curl /v1/manifest/export \
          -H "Authorization: Bearer $API_KEY" \
          -o mixpeek.yaml

        # Export specific namespace

        curl "/v1/manifest/export?namespace_id=ns_abc123" \
          -H "Authorization: Bearer $API_KEY" \
          -o namespace.yaml
        ```
      operationId: export_manifest_get_v1_manifest_export_get
      parameters:
        - name: namespace_id
          in: query
          required: false
          schema:
            type: string
            description: Export specific namespace (None = all)
            title: Namespace Id
          description: Export specific namespace (None = all)
        - name: format
          in: query
          required: false
          schema:
            type: string
            description: Output format (yaml)
            default: yaml
            title: Format
          description: Output format (yaml)
        - name: manifest_name
          in: query
          required: false
          schema:
            type: string
            description: Name for the manifest
            default: exported-manifest
            title: Manifest Name
          description: Name for the manifest
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    ErrorResponse:
      properties:
        success:
          type: boolean
          title: Success
          description: Always false for error responses
          default: false
        status:
          type: integer
          title: Status
          description: HTTP status code for this error
        error:
          $ref: '#/components/schemas/ErrorDetail'
          description: Error details payload
      type: object
      required:
        - status
        - error
      title: ErrorResponse
      description: Error response model.
      examples:
        - error:
            details:
              id: ns_123
              resource: namespace
            message: Namespace not found
            type: NotFoundError
          status: 404
          success: false
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ErrorDetail:
      properties:
        message:
          type: string
          title: Message
          description: Human-readable error message
        type:
          type: string
          title: Type
          description: Stable error type identifier (machine-readable)
        code:
          anyOf:
            - type: string
            - type: 'null'
          title: Code
          description: >-
            Fine-grained error code for programmatic handling (e.g.,
            namespace_name_taken, feature_extractor_not_found). Present only
            when consumers may need to branch on a specific error condition.
        details:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Details
          description: >-
            Optional structured details to help debugging (validation errors,
            IDs, etc.)
      type: object
      required:
        - message
        - type
      title: ErrorDetail
      description: Error detail model.
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError

````