> ## 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.

# Enqueue a bulk contact import

> Enqueue a large contact import as an asynchronous job. Post the parsed rows (already mapped to field keys such as `phone`, `email`, `first_name`) and the job runs in the background; poll GET /api/v1/contacts/imports/{id} for progress. Set `merge_strategy` to `merge` to update existing contacts, or `skip` (the default) to leave matches untouched. Returns 503 if the import queue is unavailable so the caller can fall back to the synchronous bulk path.



## OpenAPI

````yaml /openapi.yaml post /api/v1/contacts/imports
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/contacts/imports:
    post:
      tags:
        - Contacts
      summary: Enqueue a bulk contact import
      description: >-
        Enqueue a large contact import as an asynchronous job. Post the parsed
        rows (already mapped to field keys such as `phone`, `email`,
        `first_name`) and the job runs in the background; poll GET
        /api/v1/contacts/imports/{id} for progress. Set `merge_strategy` to
        `merge` to update existing contacts, or `skip` (the default) to leave
        matches untouched. Returns 503 if the import queue is unavailable so the
        caller can fall back to the synchronous bulk path.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                rows:
                  type: array
                  items:
                    type: object
                    additionalProperties:
                      type: string
                  minItems: 1
                  maxItems: 1000000
                  description: >-
                    The rows to import, each a map of already-mapped field keys
                    to string values.
                file_name:
                  type: string
                  maxLength: 255
                  description: Original upload file name, retained for auditing.
                merge_strategy:
                  type: string
                  enum:
                    - skip
                    - merge
                  default: skip
                  description: >-
                    How to handle rows that match an existing contact. `skip`
                    leaves matches untouched; `merge` updates them.
              required:
                - rows
            example:
              file_name: q1-newsletter.csv
              merge_strategy: merge
              rows:
                - phone: '+14155552671'
                  email: ada@example.com
                  first_name: Ada
                  last_name: Lovelace
      responses:
        '202':
          description: Import accepted and queued; poll the job id for progress.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      job_id:
                        type: string
                      total_rows:
                        type: integer
                      status:
                        type: string
                        enum:
                          - pending
                  meta:
                    type: object
                    properties:
                      request_id:
                        type: string
                      timestamp:
                        type: string
                        format: date-time
              example:
                data:
                  job_id: import_01HZX9IMPORT
                  total_rows: 5000
                  status: pending
                meta:
                  request_id: req_01HZX9ABCDEF
                  timestamp: '2026-02-02T12:00:00.000Z'
components:
  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_*)

````