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

# Schedule an Outbound Call

> Schedules an outbound call for a lead. The datetime should be in the future and with iso-8601 format. If not provided, the next available time will be scheduled. If the datetime is in the past, the outbound will not be scheduled. If the outbound is already scheduled, the outbound will be rescheduled.



## OpenAPI

````yaml /Sela_API.yaml post /api/leads/{id}/schedule-outbound/
openapi: 3.0.3
info:
  title: Sela API
  version: 1.0.2
  description: >-
    Create and manage leads, configure outbound webhook subscriptions, and use
    customer-specific lead ingestion workflows. Unless an endpoint says
    otherwise, authenticate with `Authorization: Token <api-key>`.
servers:
  - url: https://api.trysela.com/
    description: Production API
security: []
tags:
  - name: Leads
    description: Create, retrieve, update, and schedule customer leads.
  - name: Call Control
    description: Pause or resume outbound calling for an API user.
  - name: Lead Types
    description: >-
      Discover lead categories and the public metadata fields accepted for each
      one.
  - name: Webhooks
    description: >-
      Manage subscriptions that deliver lead and call events to customer
      systems.
  - name: Lead Ingestion
    description: >-
      Submit provider-specific lead payloads through ingestion URLs configured
      by Sela.
  - name: File Ingestion
    description: Request temporary upload URLs for configured CSV ingestion sources.
paths:
  /api/leads/{id}/schedule-outbound/:
    post:
      tags:
        - Leads
      summary: Schedule an Outbound Call
      description: >-
        Schedules an outbound call for a lead. The datetime should be in the
        future and with iso-8601 format. If not provided, the next available
        time will be scheduled. If the datetime is in the past, the outbound
        will not be scheduled. If the outbound is already scheduled, the
        outbound will be rescheduled.
      operationId: leads_schedule_outbound_create
      parameters:
        - in: path
          name: id
          schema:
            type: integer
          description: A unique integer value identifying this lead.
          required: true
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ScheduleOutboundRequestRequest'
            examples:
              ScheduleWithDatetime:
                value:
                  next_outbound_datetime: '2025-05-24T10:00:00+00:00'
                summary: Schedule with datetime
                description: Schedule an outbound call with a specific datetime.
          application/x-www-form-urlencoded:
            schema:
              $ref: '#/components/schemas/ScheduleOutboundRequestRequest'
          multipart/form-data:
            schema:
              $ref: '#/components/schemas/ScheduleOutboundRequestRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ScheduleOutboundResponse'
              examples:
                OutboundScheduledSuccessfully:
                  value:
                    scheduled_datetime: '2025-05-24T10:00:00+00:00'
                  summary: Outbound scheduled successfully
                  description: >-
                    Returns the scheduled datetime in ISO-8601 format with
                    timezone.
          description: Outbound scheduled successfully
        '400':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DetailErrorResponse'
              examples:
                InvalidDatetimeFormat:
                  value:
                    detail: >-
                      time data '2025-05-25T00:00:00' does not match format
                      '%Y-%m-%dT%H:%M:%S%z'
                  summary: Invalid datetime format
                DatetimeIsInThePast:
                  value:
                    detail: 'Provided datetime is in the past: 2025-05-24T10:00:00Z.'
                  summary: Datetime is in the past
                OutboundNotScheduled:
                  value:
                    detail: 'Outbound not scheduled for lead: 123.'
                  summary: Outbound not scheduled
          description: Bad Request, usually due to datetime format issues.
        '404':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DetailErrorResponse'
              examples:
                LeadNotFound:
                  value:
                    detail: No Lead matches the given query.
                  summary: Lead not found
          description: Lead not found
      security:
        - tokenAuth: []
      x-codeSamples:
        - lang: curl
          label: ScheduleWithDatetime
          source: |-
            curl --request POST \
              --url https://api.trysela.com/api/leads/<lead-id>/schedule-outbound/ \
              --header 'Authorization: Token <api-key>' \
              --header 'Content-Type: application/json' \
              --data '{
                "next_outbound_datetime": "2025-05-24T10:00:00+00:00"
              }'
components:
  schemas:
    ScheduleOutboundRequestRequest:
      type: object
      properties:
        next_outbound_datetime:
          type: string
          nullable: true
          description: >-
            Datetime in the future with '%Y-%m-%dT%H:%M:%S%z' format. If not
            provided, the next available time will be scheduled.
    ScheduleOutboundResponse:
      type: object
      description: Document the scheduled outbound response.
      properties:
        scheduled_datetime:
          type: string
          format: date-time
          description: Datetime when the outbound call was scheduled.
      required:
        - scheduled_datetime
    DetailErrorResponse:
      type: object
      description: Document the standard DRF error response.
      properties:
        detail:
          type: string
      required:
        - detail
  securitySchemes:
    tokenAuth:
      type: apiKey
      in: header
      name: Authorization
      description: Token-based authentication with required prefix "Token"

````