---
title: "Ingest Ringcentral Call Lead"
method: POST
path: "/leads/ingest/ringcentral-call"
tags: ["authenticated", "leads"]
---

# Ingest Ringcentral Call Lead

`POST /leads/ingest/ringcentral-call`

## Request

- Base URL: `https://api-docs.upsmith.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api-docs.upsmith.com/leads/ingest/ringcentral-call`
- Auth: one of:
  - API key in header `x-api-key`
  - HTTP bearer

Ingest a missed inbound RingCentral call as a Lead.

The RingCentral counterpart to the ServiceTitan call ingest, and suppresses
customer engagement the same way: the CRM sync creates or links the contact so a
campaign trigger can resolve it, but the intake itself sends nothing.

Idempotent on ``(organization_id, "ringcentral_call", call_id)``, which is what
lets the webhook and the poll backstop both report a call without minting twice.

## Headers

- `organization-id` string, nullable
- `x-user-id` string, nullable
- `timezone` string
- `x-actor-email` string, nullable
- `x-request-source` string, nullable
- `x-operation-id` string, nullable
- `x-commit-message` string, nullable
- `x-confirmation-id` string, nullable
- `x-chat-id` string, nullable

## Request body

- RingCentralCallIngestRequest
  - `organization_id` string, required
  - `payload` object, required

## Response `200`

Successful Response

- RingCentralCallIngestResponse
  - `lead_id` string, required
  - `created` boolean, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/upsmith/apis/upsmith-api.md) - [All operations](https://skmtc.dev/upsmith/apis/upsmith-api/llms.txt) - [OpenAPI document](https://skmtc.dev/upsmith/apis/upsmith-api/revisions/86e2c2bd93af?raw)