Live Direct Marketing System Brief Intake API

The SystemBriefIntake API from Live Direct Marketing — 2 operation(s) for systembriefintake.

Operations 2

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

GET /api/internal/brief-intake/limits Get the brief intake limits · System brief intake controller limits #
Ask an LLM
“What limits apply to submitting briefs through the internal intake?”
“How many briefs can the system intake accept?”
Tell an agent
Show the brief intake limits.
Get the current quota for internal brief intake.
POST /api/internal/brief-intake Submit a brief to the internal intake · System brief intake controller receive #
Ask an LLM
“How does a system send a brief into the intake queue?”
“Can I push a new brief through the internal intake endpoint?”
Tell an agent
Submit this brief to the internal intake.
Push a new brief into the system intake queue.

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-systembriefintake-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-systembriefintake-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: LDM v3 System Brief Intake 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: SystemBriefIntake
paths:
  /api/internal/brief-intake/limits:
    get:
      operationId: SystemBriefIntakeController_limits
      parameters:
      - name: X-Tenant-Id
        in: header
        required: false
        schema:
          type: string
          format: uuid
        description: Tenant UUID — required for all tenant-scoped endpoints
      responses:
        '200':
          description: ''
      tags:
      - SystemBriefIntake
      summary: System brief intake controller limits
      x-summary-source: derived
  /api/internal/brief-intake:
    post:
      operationId: SystemBriefIntakeController_receive
      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/Buffer'
      responses:
        '200':
          description: ''
      tags:
      - SystemBriefIntake
      summary: System brief intake controller receive
      x-summary-source: derived
components:
  schemas:
    Buffer:
      type: object
      properties: {}
  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.