VectorMethods

Docs / API reference

Exports

Export VideoVector metadata by index or prompt run, then retrieve download or connector-delivery status.

api/routes.pysdk/videovector/resources/exports.pyfrontend/src/services/api.ts

Search documentation

Search pages, API reference sections, and guide headings.

Summary

Exports package run-backed metadata for download or connector delivery. The public API supports export creation by index or run plus status retrieval and listing.

Export endpoints

MethodPathPurpose
POST/api/v2/exports/index/{index_id}Create an index export
POST/api/v2/exports/prompt-run/{run_id}Create a prompt-run export
GET/api/v2/exportsList exports
GET/api/v2/exports/{export_id}Retrieve one export

Export request fields

Index exports support:

  • optional prompt_run_ids
  • optional destination_connector_id
  • optional destination_subpath

Prompt-run exports support:

  • optional destination_connector_id
  • optional destination_subpath

Example: export selected runs from an index

curl -X POST /api/v2/exports/index/idx_archive \
  -H "X-API-Key: sk_live_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: export-archive-review" \
  -d '{
    "prompt_run_ids": ["run_123", "run_124"],
    "destination_connector_id": "conn_export",
    "destination_subpath": "exports/review-team"
  }'

Status model

The SDK exposes these public export statuses:

  • pending
  • processing
  • completed
  • failed

Completed exports may provide a download URL, connector-delivery metadata, or both depending on the requested destination mode.

SDK equivalents

  • client.exports.create_index_export
  • client.exports.create_prompt_run_export
  • client.exports.retrieve
  • client.exports.list

Related documentation

Use exports to package result data for download or connector delivery, then use export automations when the handoff should persist per index.

API reference

Automations watch connector paths, trigger prompt presets, and deliver index exports for recurring VideoVector workflows.

API reference

Connectors are the public storage integration boundary for import and export workflows. The API supports provider-specific creation, listing, retrieval, testing, browsing, update, and deletion.