Manifest

Compare a manifest file with current state.

Shows resources that would be:

  • Created: In manifest but not in system
  • In system only: In system but not in manifest
  • Different: In both but with configuration differences

This is useful for understanding what changes would occur before applying a manifest.

Example:

curl -X POST /v1/manifest/diff \
  -H "Authorization: Bearer $API_KEY" \
  -F "manifest_file=@mixpeek.yaml"
post/v1/manifest/diff

Request

  • Base URL: https://api.mixpeek.com
  • URL: https://api.mixpeek.com/v1/manifest/diff
  • Auth: HTTP bearer

Request body multipart/form-data

manifest_filestring binary required

YAML manifest file

parametersstring nullable

JSON object of values for the manifest's declared parameters, e.g. {"camera_url": "rtsp://host/stream", "polling_seconds": 300}. Each value must match its declared type. Omit when the manifest declares none.

Response

Successful Response

Changes

    • info

      added the new optional request property

    • warning

      removed the optional property from the response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the optional property to the response with the status

    • info

      added the required property to the response with the status

    • info

      added the required property to the response with the status