> ## Documentation Index > Fetch the complete documentation index at: https://docs.vorel.ai/llms.txt > Use this file to discover all available pages before exploring further. # Escalate a lead to human handoff > Flips the lead's underlying conversation to `awaiting_human` + audit-logs the trigger + publishes the `conversation.handoff_requested` webhook event. Mirrors the internal `request_handoff` tool but for operator-initiated escalation (e.g. nurture-loop day 7, post-call no-response). Re-posting flips status (no-op if already awaiting_human) and writes a fresh audit row + handoff_id; operators who want strict idempotency should include their own dedupe key in the workflow. ## OpenAPI ````yaml https://app.vorel.ai/api/v1/openapi.json post /api/v1/leads/{id}/handoff openapi: 3.1.0 info: title: Vorel API version: 0.1.0 description: >- Public API for Vorel — the AI receptionist for any business. Read your conversations, leads, appointments, and catalog; push CRM-side updates back into the platform. All endpoints accept bearer-auth API keys issued at `/settings/integrations/api-keys` in the dashboard. Per-key rate limit is 200 req/min. contact: name: Vorel support email: hello@vorel.ai license: name: Proprietary servers: - url: https://app.vorel.ai description: Production - url: http://localhost:3000 description: Local dev security: - BearerAuth: [] tags: - name: Conversations description: Inbound customer conversations across channels. - name: Leads description: Qualified-lead rows attached to conversations. - name: Appointments description: Scheduled customer engagements. - name: Offerings description: Tenant catalog (properties, services, treatments — vertical-specific). - name: Analytics description: >- Aggregate metrics for tenant + automation consumers. The around-the-brain workflows read these rather than mass-querying the resource endpoints. - name: CRM description: >- Operator-side writes into the tenant's configured CRM (HubSpot / Salesforce / Zoho / etc.). Per-tenant field mappings translate canonical Vorel keys to vendor-side keys before the driver call. paths: /api/v1/leads/{id}/handoff: post: tags: - Leads summary: Escalate a lead to human handoff description: >- Flips the lead's underlying conversation to `awaiting_human` + audit-logs the trigger + publishes the `conversation.handoff_requested` webhook event. Mirrors the internal `request_handoff` tool but for operator-initiated escalation (e.g. nurture-loop day 7, post-call no-response). Re-posting flips status (no-op if already awaiting_human) and writes a fresh audit row + handoff_id; operators who want strict idempotency should include their own dedupe key in the workflow. operationId: handoffLead parameters: - name: id in: path required: true schema: type: string format: uuid description: UUID of the lead to escalate. requestBody: required: false content: application/json: schema: $ref: '#/components/schemas/LeadHandoffBody' responses: '200': description: Handoff recorded. content: application/json: schema: $ref: '#/components/schemas/LeadHandoffResponse' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/RateLimited' security: - BearerAuth: - leads:write components: schemas: LeadHandoffBody: type: object description: >- Both fields optional. Defaults are written into the audit log so the trail is never empty. properties: reason: type: string maxLength: 200 description: Short-form trigger label (e.g. 'no-response-7d'). summary: type: string maxLength: 1000 description: Free-form context for the human picking up the conversation. LeadHandoffResponse: type: object required: - handoff_id - lead_id - conversation_id - conversation_status - notified_channel properties: handoff_id: type: string format: uuid lead_id: type: string format: uuid conversation_id: type: string format: uuid conversation_status: type: string enum: - awaiting_human notified_channel: type: string enum: - slack - email ErrorEnvelope: type: object required: - error properties: error: type: object required: - code - message properties: code: type: string enum: - unauthorized - forbidden - rate_limited - bad_request - not_found - conflict - internal_error description: Machine-readable error category. message: type: string description: >- Human-readable error description; safe to surface in tenant logs. responses: BadRequest: description: Body validation failed. Error message names the offending field. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' Unauthorized: description: Missing, malformed, unknown, or revoked API key. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' Forbidden: description: >- API key is valid but lacks the required scope for this endpoint. Issue a new key with the necessary scope at `/settings/integrations/api-keys`. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' NotFound: description: >- A referenced resource (e.g. `conversation_id` on a lead create, or any of the optional FK targets on an appointment create) is not visible to your tenant. Cross-tenant rows return the same envelope as truly-non-existent rows — this is intentional to prevent enumeration. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' RateLimited: description: >- 200 req/min per API key exceeded. `Retry-After` header carries seconds-until-reset. headers: Retry-After: schema: type: integer X-RateLimit-Limit: schema: type: integer X-RateLimit-Remaining: schema: type: integer X-RateLimit-Reset: schema: type: integer description: Unix epoch seconds. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: vapk__<48-hex> description: >- Tenant-issued API key. Format: `vapk_live_<48 hex chars>` (60 chars total). Issue + manage at `/settings/integrations/api-keys` in the Vorel dashboard. Each key has a scope set (`read`, `leads:write`, `appointments:write`, `offerings:write`); endpoints requiring a write scope reject keys without it with a 403 envelope. ````