Skip to main content
This feature is currently limited. Contact us to enable.
Use SFTP as a managed transport layer for the same Batch Inference jobs covered in this section. Drop files into the inbound folder, Avra submits them to the Batch API on your behalf, and results land back in the outbound folder with full observability via webhooks and dashboard events.

​
Prerequisites

  • Batch prediction target configured in production ({model_id}/production, {model_id}/challenger, or {model_id}/{version_id})
  • At least one SFTP user provisioned by Avra Ops
  • IP allowlist entries (if required by your network policies)
  • Optional: webhook subscription for batch-lifecycle

​
Directory Layout

batch/
  in/
    batch_2025-05-01.jsonl
    batch_2025-06-01.parquet
  out/
    batch_2025-05-01.jsonl
    batch_2025-06-01.parquet
logs/
samples/

​
File Format

CSV or JSONL up to 5 GB and 1,000,000 rows per file. Required columns:
  • endpoint: the model prediction target, using the same model_id + alias or version convention as the Prediction API (e.g. {model_id}/production, {model_id}/challenger, {model_id}/{version_id})
  • All inputs declared in the model’s schema (e.g. legal_document, avra__internal__customer_embedding)
  • Optional metadata columns (correlation_id, reference_id) are echoed back in the output.

​
Processing Flow

See Batch Inference for service-level expectations, retries, and status polling flow. Pair with webhook notifications to receive completion callbacks without polling SFTP.