> ## Documentation Index > Fetch the complete documentation index at: https://bavlio.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Schedule Inbox Draft > Schedule a draft (pending|approved -> scheduled) AND enroll it into the dispatch queue. The future-instant + DST-gap checks run SERVER-SIDE (a wall-clock+timezone is resolved via ZoneInfo, spring-forward gaps rejected); the per-org daily-schedule cap is enforced atomically inside the seam RPC. Scheduling now ATOMICALLY upserts the content_scheduled_posts dispatch row (E4.1b), so the dispatcher actually publishes the post. 404 if not owned, 409 if not pending/approved, 422 on a past/DST-gap time, 429 when the daily cap is hit. ## OpenAPI ````yaml https://api.bavlio.com/openapi.json post /api/v1/content/inbox/{draft_id}/schedule openapi: 3.1.0 info: title: Bavlio API description: >- Outreach automation API — lead enrichment, email campaigns, LinkedIn automation, and AI agent. Full docs at https://docs.bavlio.com. version: 1.0.0 x-guidance: product: Bavlio Data API protocols: - x402 description: >- Pay-per-call B2B data endpoints for AI agents. USDC on Base mainnet via x402 v2. See /openapi.json for pricing. Landing page + marketing details: https://bavlio.com/developers network: eip155:8453 docs_url: https://docs.bavlio.com x-payment-merchant-address: '0xcca4725e0e931982830bff523b141e1a7a58d3e7' servers: [] security: [] tags: - name: API Keys description: >- Create, list, and revoke API keys for programmatic access. JWT authentication required. - name: credits description: Credit balance, cost estimates, and transaction history. - name: campaigns description: Create, manage, launch, and monitor email campaigns. - name: campaign-personalization description: AI-powered email subject and body personalization for campaigns. - name: email-finder description: Find and verify email addresses for prospects. - name: sender-profiles description: Manage sender identity profiles for outreach. - name: sender-profile-chat description: Interactive chat for building sender profiles. - name: templates description: Email template CRUD. - name: suppression description: Do-not-contact suppression list management. - name: datasets description: Lead dataset listing, download, and updates. - name: user-extractions description: Uploaded lead file management and processing. - name: enrichment-chat description: Interactive chat for data enrichment sessions. - name: enrichment-processing description: Batch lead enrichment processing. - name: File Upload (CSV/Excel) description: Upload and preview CSV/Excel lead files. - name: connected-accounts description: LinkedIn account connections via Unipile. - name: linkedin-content description: LinkedIn post creation, scheduling, and management. - name: linkedin-playground description: Direct LinkedIn actions (profile lookup, messaging, engagement). - name: bavimail-proxy description: BaviMail domain, alias, and email management. - name: agent description: Bavi AI agent chat with SSE streaming. - name: notifications description: Notification preferences and delivery. - name: referral description: Referral code management and stats. - name: feedback description: User feedback submission. - name: authentication description: JWT token verification and user info. - name: users description: User quota and usage information. - name: Health description: Health checks and system status. - name: Personalization description: Core lead personalization engine. - name: Session Management description: Enrichment session lifecycle. - name: Session Processing description: Session data processing. - name: webhooks description: Inbound webhook handlers (Stripe, BaviMail, Unipile). paths: /api/v1/content/inbox/{draft_id}/schedule: post: tags: - content_inbox summary: Schedule Inbox Draft description: >- Schedule a draft (pending|approved -> scheduled) AND enroll it into the dispatch queue. The future-instant + DST-gap checks run SERVER-SIDE (a wall-clock+timezone is resolved via ZoneInfo, spring-forward gaps rejected); the per-org daily-schedule cap is enforced atomically inside the seam RPC. Scheduling now ATOMICALLY upserts the content_scheduled_posts dispatch row (E4.1b), so the dispatcher actually publishes the post. 404 if not owned, 409 if not pending/approved, 422 on a past/DST-gap time, 429 when the daily cap is hit. operationId: schedule_inbox_draft_api_v1_content_inbox__draft_id__schedule_post parameters: - name: draft_id in: path required: true schema: type: string format: uuid title: Draft Id requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ContentDraftScheduleRequest' responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/ContentDraftResponse' '401': description: Unauthorized '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - HTTPBearer: [] components: schemas: ContentDraftScheduleRequest: properties: scheduled_at: anyOf: - type: string format: date-time - type: 'null' title: Scheduled At local_datetime: anyOf: - type: string format: date-time - type: 'null' title: Local Datetime timezone: anyOf: - type: string - type: 'null' title: Timezone provider_account_id: anyOf: - type: string maxLength: 255 minLength: 1 - type: 'null' title: Provider Account Id description: >- LinkedIn OAuth account to pin for this scheduled post. Omit to snapshot the org's LinkedIn default when the dispatch row is created. linkedin_account_id: anyOf: - type: string maxLength: 200 - type: 'null' title: Linkedin Account Id x_account_id: anyOf: - type: string maxLength: 200 - type: 'null' title: X Account Id type: object title: ContentDraftScheduleRequest description: >- Schedule a draft to publish at a future instant. Two input shapes (exactly one): an ABSOLUTE ``scheduled_at`` (tz-aware), OR a per-tenant wall-clock ``local_datetime`` (naive) + IANA ``timezone``. The server resolves the wall-clock via ZoneInfo, rejects past-time + DST-gap, and enforces the per-day cap. Scheduling enrolls the draft into the dispatch queue (E4.1b). ContentDraftResponse: properties: id: type: string format: uuid title: Id status: type: string enum: - pending - approved - denied - snoozed - scheduled title: Status linkedin_body: anyOf: - type: string - type: 'null' title: Linkedin Body x_body: anyOf: - type: string - type: 'null' title: X Body media_asset_id: anyOf: - type: string format: uuid - type: 'null' title: Media Asset Id media_asset_ids: items: type: string format: uuid type: array title: Media Asset Ids scheduled_at: anyOf: - type: string format: date-time - type: 'null' title: Scheduled At voice_config_snapshot: anyOf: - additionalProperties: true type: object - type: 'null' title: Voice Config Snapshot source: anyOf: - type: string - type: 'null' title: Source topic: anyOf: - type: string - type: 'null' title: Topic created_at: type: string format: date-time title: Created At updated_at: type: string format: date-time title: Updated At type: object required: - id - status - created_at - updated_at title: ContentDraftResponse description: >- A single Inbox draft card (list-row + get + action responses). NEVER includes ``dedupe_key`` (internal CAS key). ``voice_config_snapshot`` is the voice config stamped at generate time (E3.1); the UI may render it read-only. HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: HTTPBearer: type: http scheme: bearer ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.