Live Direct Marketing Marking API

The Marking API from Live Direct Marketing — 5 operation(s) for marking.

Operations 6

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/marking/patterns List message marking patterns · List all marking patterns #
Ask an LLM
“Which patterns are used to auto-mark incoming replies?”
“Can I list only enabled marking patterns for a given result?”
Tell an agent
List marking patterns with result {result} and enabled {enabled}.
Show enabled={enabled} patterns that mark messages as {result}.
POST /api/marking/patterns Create a marking pattern · Create a new marking pattern #
Ask an LLM
“How do I add a new rule for automatically marking replies?”
“Can I define my own message marking pattern?”
Tell an agent
Create a new marking pattern.
Add a pattern for auto-marking incoming messages.
PATCH /api/marking/patterns/{id}/toggle Enable or disable a marking pattern · Enable or disable a marking pattern #
Ask an LLM
“Can I switch off a marking pattern without deleting it?”
“How do I re-enable a disabled marking pattern?”
Tell an agent
Toggle marking pattern {id} on or off.
Disable marking pattern {id}.
DELETE /api/marking/patterns/{id} Delete a marking pattern · Delete a marking pattern #
Ask an LLM
“How do I permanently remove a marking pattern?”
“Can I delete a reply-marking rule I no longer want?”
Tell an agent destructive · confirm first
Delete marking pattern {id}.
Remove pattern {id} from message marking.
POST /api/marking/classify Classify a message text against marking patterns · Classify a message against the marking patterns #
Ask an LLM
“Which marking pattern would a given message text match?”
“Can I test a sample reply against my marking rules?”
Tell an agent
Classify this message against the marking patterns.
Test a sample reply text against my marking rules.
POST /api/marking/dialogs/{id}/classify Classify a dialog against marking patterns · Classify a specific dialog against the marking patterns #
Ask an LLM
“How would an existing conversation be marked by my patterns?”
“Can I run marking classification on one specific dialog?”
Tell an agent
Classify dialog {id} with the marking patterns.
Check which marking pattern dialog {id} matches.

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-marking-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-marking-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: LDM v3 Marking 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: Marking
paths:
  /api/marking/patterns:
    get:
      operationId: MarkingController_listPatterns
      parameters:
      - name: result
        required: true
        in: query
        schema:
          type: string
      - name: enabled
        required: true
        in: query
        schema:
          type: string
      - 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: ''
      security:
      - jwt: []
      summary: List all marking patterns
      tags:
      - Marking
      x-required-scope:
      - marking:read
    post:
      operationId: MarkingController_createPattern
      parameters:
      - name: X-Tenant-Id
        in: header
        required: false
        schema:
          type: string
          format: uuid
        description: Tenant UUID — required for all tenant-scoped endpoints
      responses:
        '201':
          description: ''
      security:
      - jwt: []
      summary: Create a new marking pattern
      tags:
      - Marking
      x-required-scope:
      - marking:write
  /api/marking/patterns/{id}/toggle:
    patch:
      operationId: MarkingController_togglePattern
      parameters:
      - name: id
        required: true
        in: path
        schema:
          type: number
      - 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: ''
      security:
      - jwt: []
      summary: Enable or disable a marking pattern
      tags:
      - Marking
  /api/marking/patterns/{id}:
    delete:
      operationId: MarkingController_deletePattern
      parameters:
      - name: id
        required: true
        in: path
        schema:
          type: number
      - 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: ''
      security:
      - jwt: []
      summary: Delete a marking pattern
      tags:
      - Marking
  /api/marking/classify:
    post:
      operationId: MarkingController_classify
      parameters:
      - name: X-Tenant-Id
        in: header
        required: false
        schema:
          type: string
          format: uuid
        description: Tenant UUID — required for all tenant-scoped endpoints
      responses:
        '201':
          description: ''
      security:
      - jwt: []
      summary: Classify a message against the marking patterns
      tags:
      - Marking
      x-required-scope:
      - marking:read
  /api/marking/dialogs/{id}/classify:
    post:
      operationId: MarkingController_classifyDialog
      parameters:
      - name: id
        required: true
        in: path
        schema:
          type: string
      - name: X-Tenant-Id
        in: header
        required: false
        schema:
          type: string
          format: uuid
        description: Tenant UUID — required for all tenant-scoped endpoints
      responses:
        '201':
          description: ''
      security:
      - jwt: []
      summary: Classify a specific dialog against the marking patterns
      tags:
      - Marking
components:
  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.