Live Direct Marketing A2A API

The A2A API from Live Direct Marketing — 1 operation(s) for a2a.

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/a2a Send an A2A JSON-RPC request · A2A JSON-RPC 2.0 dispatch (single or batch, supports SSE for streaming methods) #
Ask an LLM
“Can an agent talk to Live Direct Marketing over the A2A protocol?”
“Does the A2A endpoint support batched calls and streaming responses?”
Tell an agent
Send A2A method {method} with params {params} and request id {id}.
Call A2A method {method} using JSON-RPC version {jsonrpc}.

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

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

OpenAPI Specification

live-direct-marketing-online-a2a-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: LDM v3 A2A 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: a2a
paths:
  /api/a2a:
    post:
      operationId: A2AController_dispatch
      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
        description: Single JSON-RPC 2.0 request. A JSON array of requests (batch, §6) is also accepted at runtime — documented shape here is the single-request form.
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/A2ABodyDto'
      responses:
        '200':
          description: ''
      security:
      - jwt: []
      summary: A2A JSON-RPC 2.0 dispatch (single or batch, supports SSE for streaming methods)
      tags:
      - a2a
components:
  schemas:
    A2ABodyDto:
      type: object
      properties:
        jsonrpc:
          type: string
          enum:
          - '2.0'
          description: JSON-RPC 2.0 protocol marker
        id:
          type:
          - object
          - 'null'
          description: 'Request id: string, number, or null (JSON-RPC 2.0)'
        method:
          type: string
          description: A2A JSON-RPC method, e.g. message/send, tasks/get, tasks/cancel
        params:
          type: object
          description: Method-specific params object
      required:
      - jsonrpc
      - id
      - method
  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.