Trigger a manual fetch-and-ingest from an external transport
Lists every object matching the supplied transport coordinates and streams each into the trusted-content ingestion pipeline (dedup + outbox + match-trigger), returning a per-file outcome in fetch order. The tenant is resolved from the JWT and the context/source from the path — NEVER from the body. The body carries connection coordinates plus an OPAQUE credential reference. A transport-level fetch failure (the external endpoint is unreachable or rejects the credential) returns 503; per-file intake failures are reported in the response body without failing the batch.
POST
Trigger a manual fetch-and-ingest from an external transport
Autorizaciones
Cuerpo
application/json

