Download a finished job's sales report.

Renders the job's sales report on request: the same document the Telegram bot sends when a job completes (executive summary, immediate actions, one outreach draft per delivered prospect, and the prospect table), without going through the bot. Read-only: it starts no job, sends nothing to Telegram and changes nothing about the job.

Credits. Free. Fetching the report is a read of a document the job's own charge already covers, so it neither debits credits nor takes an Idempotency-Key. It is subject to the standard per-customer rate limit (100 requests / 60 s). The first request for a language the job has not been rendered in yet may take longer (up to a few minutes for a large cohort), because the report text is written then and cached for later requests.

Formats. format=pdf (default) returns application/pdf; format=html returns the self-contained HTML page the PDF is rendered from (text/html), which is convenient for reading or asserting on the text without a PDF parser.

Language. lang is an ISO 639-1 code from the supported set below. Default: the language the job was started in, else en. Company and person names are never translated.

Availability. Only a completed or exhausted job that delivered at least one prospect has a report; any other state answers 409 report_not_available. A job that belongs to another tenant, a job id that does not exist and a job that has expired all answer the same 403 not_owner at the gateway, so an id's existence is never confirmed.

Cost controls. Only generating a report that is not cached yet costs anything. Concurrent requests for the same report share one generation: the others wait briefly, then are served, or answer 409 report_rendering with Retry-After. A customer's newly generated reports are capped per UTC day (429 report_quota_exceeded, Retry-After); already generated reports stay available. A generation that fails does not use up the daily limit, and requests that were waiting on it are told at once (502 render_failed, Retry-After). If report generation is temporarily unavailable it answers 503 report_gate_unavailable with Retry-After instead of starting an unguarded generation.