Menu

Recordings

1 endpoint in the Mattering Productivity API.

POST recordings/extract/ User APIService tier

Recording-frame extraction stub.

The full implementation called an external worker (RECORDING_FRAME_EXTRACTOR_WORKER_URL) and persisted the result onto execution_payload['nodes'][node_id]. That path was removed along with the rest of the automation engine in commit 4789a12 and has not been reimplemented here yet: restoring it requires bringing back _resolve_recording_context_inputs, _rewrite_extract_frames_to_proxied_urls, _frames_to_markdown, _strip_frame_metadata, plus settings (MATTERING_PM_PUBLIC_BASE_URL, RECORDING_FRAME_EXTRACTOR_WORKER_URL, RECORDING_PIPELINE_SHARED_SECRET).

Until then this endpoint returns a clear not_implemented error so callers fail loudly instead of hanging on the deleted _av()._exec_* AttributeError.

URL

  • User APIhttps://productivity.mattering.io/api/user/v1/recordings/extract/
  • Service tierhttps://productivity.mattering.io/api/internal/recordings/extract/

Errors

StatusCode
501not_implemented

Example

curl -X POST "https://productivity.mattering.io/api/user/v1/recordings/extract/" \
  -H "Authorization: Bearer $MATTERING_API_KEY"

Source: MatteringPMCore/internal_api.py (internal_api.internal_extract_recording_context)

All Productivity resources
Start Free Explore our Products