> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Receive a Salesforce webhook event

> Ingests Salesforce CRM change events (Contact, Lead, Account, Opportunity, Case create/update/delete and Task create) delivered via Outbound Messages, an Apex callout, or a Change-Data-Capture relay, and mirrors them into tenant state so campaign triggers fire in real time. The `org_id` in the body routes to the connected tenant and the `X-Devotel-Sf-Signature` HMAC is the authentication — Salesforce calls this endpoint, not your application. Re-deliveries dedupe on `event_uuid`.



## OpenAPI

````yaml /openapi.yaml post /api/v1/integrations/webhooks/salesforce
openapi: 3.1.0
info:
  title: Devotel CPaaS API
  description: Orbit by Devotel — Communications Platform as a Service API
  version: 1.0.0
  contact:
    name: Devotel
    url: https://devotel.io
    email: support@devotel.io
  license:
    name: Proprietary
servers:
  - url: https://api.orbit.devotel.io
    description: Production
security:
  - Bearer: []
  - ApiKey: []
tags:
  - name: Messages
    description: >-
      Send and manage messages across all channels (SMS, WhatsApp, RCS, Email,
      Viber, etc.)
  - name: Fax
    description: >-
      List and track fax (MMS/T.38) transmissions on Telnyx-backed fax numbers
      (sending flows through the Messaging API)
  - name: Agents
    description: AI agent creation, configuration, and execution
  - name: Voice
    description: Voice calls, IVR, conferencing, and SIP trunking
  - name: OnCall
    description: On-call rotations and escalation policy planning for incident alerting
  - name: Webhooks
    description: Webhook endpoint management and delivery logs
  - name: Numbers
    description: Phone number search, provisioning, and configuration
  - name: Brand Identity
    description: >-
      Unified cross-channel brand trust posture (10DLC, toll-free, WhatsApp,
      RCS, branded calling, number KYC)
  - name: Contacts
    description: Contact management, segmentation, and lifecycle tracking
  - name: Campaigns
    description: Marketing campaign orchestration and analytics
  - name: Flows
    description: Automation flow builder and execution engine
  - name: Templates
    description: Message template management and approval workflows
  - name: Settings
    description: Organization, channel, and user preference settings
  - name: Verify
    description: OTP generation and verification across channels
  - name: Push
    description: Push notification delivery via FCM and APNs
  - name: Integrations
    description: Third-party service connections and OAuth management
  - name: CDP
    description: >-
      Customer Data Platform — activation surface (CRM object sync, streaming
      destinations, ad-audience activation)
  - name: Files
    description: >-
      Server-to-server media upload, listing, retrieval, and deletion
      (signed-URL backed)
  - name: Commerce
    description: >-
      Omnichannel conversational-commerce — persistent cart + checkout state
      machine, channel-agnostic hosted pay-by-link, native WhatsApp checkout,
      and AP2-style agent payment mandates.
  - name: Sync
    description: >-
      Real-time shared-state primitive (Twilio Sync parity) — Documents, Maps,
      Lists, and ephemeral Streams, with change events relayed over the
      /api/v1/ws/sync WebSocket gateway
  - name: Risk
    description: >-
      Unified cross-channel Trust & Fraud risk scoring — fuses SMS-pumping,
      URL-reputation, Verify Fraud Guard, and Voice Biometrics signals into one
      composite verdict queryable before a send or a call.
  - name: Orby
    description: >-
      In-dashboard Orby operator assistant: streamed assistant turns,
      conversation threads, product knowledge-base search, and the tool-action
      approval gate. Available to signed-in operators only (dashboard session
      auth — API-key requests are rejected).
paths:
  /api/v1/integrations/webhooks/salesforce:
    post:
      tags:
        - Integrations
      summary: Receive a Salesforce webhook event
      description: >-
        Ingests Salesforce CRM change events (Contact, Lead, Account,
        Opportunity, Case create/update/delete and Task create) delivered via
        Outbound Messages, an Apex callout, or a Change-Data-Capture relay, and
        mirrors them into tenant state so campaign triggers fire in real time.
        The `org_id` in the body routes to the connected tenant and the
        `X-Devotel-Sf-Signature` HMAC is the authentication — Salesforce calls
        this endpoint, not your application. Re-deliveries dedupe on
        `event_uuid`.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - org_id
                - events
              additionalProperties: true
              properties:
                org_id:
                  type: string
                  description: >-
                    The Salesforce 18-character Organization Id of the sending
                    org.
                events:
                  type: array
                  description: >-
                    One or more change events, each carrying a stable
                    `event_uuid`, an `event_type`, an `occurred_at` timestamp,
                    and the changed `object`.
                  items:
                    type: object
                    additionalProperties: true
            example:
              org_id: 00D5f000000abcdEAA
              events:
                - event_uuid: 8f1d2c34-9b0e-4c1a-b2d3-1a2b3c4d5e6f
                  event_type: contact.created
                  occurred_at: '2026-08-09T12:00:00Z'
                  object:
                    Id: 0035f00000XYZ12
                    Email: dana@example.com
      responses:
        '200':
          description: The batch was received; the body reports per-event counts.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      received:
                        type: boolean
                        description: >-
                          True once the signed batch is accepted (false with a
                          `reason` when the org is not connected).
                      org_id:
                        type: string
                        description: The Salesforce Organization Id echoed back.
                      processed:
                        type: integer
                        description: Number of events applied to tenant state.
                      duplicates:
                        type: integer
                        description: Number of events skipped as idempotent replays.
                      unrecognised:
                        type: integer
                        description: Number of events whose type has no handler.
                  meta:
                    $ref: '#/components/schemas/ResponseMeta'
components:
  schemas:
    ResponseMeta:
      type: object
      required:
        - request_id
        - timestamp
      additionalProperties: false
      properties:
        request_id:
          type: string
          description: Unique request identifier (also returned as X-Request-Id header)
        timestamp:
          type: string
          format: date-time
        docs_url:
          type: string
          format: uri
          nullable: true
  securitySchemes:
    Bearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Dashboard JWT token from Clerk
    ApiKey:
      type: apiKey
      name: X-API-Key
      in: header
      description: Server-to-server API key (dv_live_sk_*)

````