Live Direct Marketing Best Send Time API

The Best Send Time API from Live Direct Marketing — 1 operation(s) for best send time.

Documentation GitHub OpenAPI

Operations 1

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /api/best-send-time Recommend the best time to send to a contact · Resolve recommended send time without scheduling; AI fallback uses normal usage… #

Ask an LLM

“When is the best time to email a particular contact?”

“Can the send-time recommendation mirror when a contact last replied?”

Tell an agent

Recommend a send time for contact {contactId}.

Find the best send time for lead {leadId} based on dialog {dialogId}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/live-direct-marketing-online:live-direct-marketing-online-best-send-time-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: LDM v3 Best Send Time API
  description: 'Multi-tenant B2B outreach automation platform. Auth: JWT Bearer (15-min) or tenant API key (ldm_*) managed in CRM Settings → API Keys. All tenant-scoped endpoints require the X-Tenant-Id header.'
  version: 1.0.0
  contact: {}
servers:
- url: https://api.live-direct-marketing.online
  description: Production
- url: https://api.dev.live-direct-marketing.online
  description: Development
- url: http://127.0.0.1:3000
  description: Local
tags:
- name: Best Send Time
paths:
  /api/best-send-time:
    post:
      operationId: BestSendTimeController_resolve
      parameters:
      - name: X-Tenant-Id
        in: header
        required: false
        schema:
          type: string
          format: uuid
        description: Tenant UUID — required for all tenant-scoped endpoints
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/BestSendTimeDto'
      responses:
        '200':
          description: ''
      security:
      - jwt: []
      summary: Resolve recommended send time without scheduling; AI fallback uses normal usage…
      tags:
      - Best Send Time
components:
  schemas:
    BestSendTimeDto:
      type: object
      properties:
        contactId:
          type: string
        leadId:
          type: string
        dossier:
          type: object
          description: Pre-built dossier (same shape as LeadsService.getDossier returns).
        dialogId:
          type: string
          description: 'If provided, enables Tier 0 ("mirror reply time"): the analyzer reads this

            inbound dialog''s createdAt, projects its (weekday, hour, minute) into the

            contact''s local TZ, and returns the next future occurrence of that slot.

            Falls back to lower tiers when the dialog is auto-reply / non-email / OUT.

            Combine with contactId/leadId to also fetch the dossier for TZ resolution.'
        now:
          type: string
          description: 'Optional reference moment (ISO). Used as "now" when computing the next

            Tue/Wed/Thu × hour slot. Defaults to current time. Useful for tests and

            for asking "what would best-send-time recommend if I asked yesterday".'
  securitySchemes:
    jwt:
      scheme: bearer
      bearerFormat: JWT
      type: http
      description: JWT access token from /auth/login (Bearer <token>)
    tenant-api-key:
      scheme: bearer
      bearerFormat: JWT
      type: http
      description: Tenant API key (Bearer ldm_*) for MCP/A2A clients. Issued via CRM Settings → API Keys.
    rpa-service:
      scheme: bearer
      bearerFormat: JWT
      type: http
      description: Dedicated RPA service key. No tenant API-key or query-key authentication.