Create Call Analysis
Submit call records for asynchronous analysis. HTTP 200 with a nonempty processing_id acknowledges receipt; per-record validation and analysis continue afterwards. Configure an analytics callback in Dashboard → Developer Hub → Configuration to receive results. Call Analytics guide. Each record supports optional lead source, CRM stage/substage, follow-up and lead creation times, location, customer phone, campaign identifiers, and tags. The full input schema below defines these fields; reprocess defaults to 0. A null processing_id means initiation was not confirmed, even with HTTP 200. Contact support before resubmitting.
Authentication
Request
Authorized project/service name from Developer Hub.
Between 1 and 20 records per batch. Per-record CRM, campaign, tag fields are described below.
Response
Batch initiation result. Acceptance requires a nonempty processing_id; a null value does not confirm acceptance.
Batch identifier for tracking processing results. Acceptance requires a nonempty identifier. The existing endpoint can return HTTP 200 with null when initiation fails; contact support before resubmitting.