Live Direct Marketing Tracking / Bot List API

The Tracking / Bot List API from Live Direct Marketing — 4 operation(s) for tracking / bot list.

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/bot-list Get global bot-list stats · Bot-list stats (feed count, custom CIDR/UA, last refresh). #
Ask an LLM
“How many bot feeds and custom IP ranges are on the global bot list?”
“When was the click-tracking bot list last refreshed?”
Tell an agent
Show the global bot-list stats.
Report the bot feed count, custom entries and last refresh time.
POST /api/bot-list/refresh Reload external bot feeds now · Reload external bot-feeds now (BOT_FEED_URLS) into the in-memory matcher. #
Ask an LLM
“Can I force the bot feeds to reload instead of waiting for the schedule?”
“How do I pull the latest external bot lists into the matcher right away?”
Tell an agent
Refresh the external bot feeds now.
Reload the bot-list matcher from its feeds immediately.
POST /api/bot-list/cidr Add an IP range to the global bot list · Add a custom bot CIDR to the GLOBAL bot-list (e.g. #
Ask an LLM
“How do I flag clicks from a whole IP range as bot traffic?”
“Can I add a custom CIDR so those clicks go to the decoy URL?”
Tell an agent
Add a custom bot CIDR to the global bot list.
Mark an IP range as bots for every tenant's split-cloaked links.
DELETE /api/bot-list/cidr Remove an IP range from the global bot list · Remove a custom bot CIDR from the GLOBAL bot-list. SUPER-only #
Ask an LLM
“How do I stop treating an IP range as bot traffic?”
“Can I take a custom CIDR back off the bot list?”
Tell an agent destructive · confirm first
Remove a custom bot CIDR from the global bot list.
Delete an IP range from the custom bot entries.
POST /api/bot-list/ua Add a user-agent pattern to the bot list · Add a custom bot User-Agent regex to the GLOBAL bot-list (e.g. #
Ask an LLM
“Can I mark clicks from a specific crawler's user agent as bots?”
“How do I add a user-agent regex to the global bot list?”
Tell an agent
Add a custom bot user-agent regex to the global bot list.
Treat a scanner's user agent as a bot across all tenants.
DELETE /api/bot-list/ua Remove a user-agent pattern from the bot list · Remove a custom bot User-Agent regex from the GLOBAL bot-list. SUPER-only #
Ask an LLM
“How do I unflag a user agent I previously marked as a bot?”
“Can I delete a custom user-agent regex from the bot list?”
Tell an agent destructive · confirm first
Remove a custom bot user-agent regex from the global bot list.
Stop treating a user-agent pattern as a bot.

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-tracking-bot-list-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-tracking-bot-list-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: LDM v3 Tracking / Bot List 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: Tracking / Bot List
paths:
  /api/bot-list:
    get:
      operationId: BotListController_stats
      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: ''
      security:
      - jwt: []
      summary: Bot-list stats (feed count, custom CIDR/UA, last refresh).
      tags:
      - Tracking / Bot List
  /api/bot-list/refresh:
    post:
      operationId: BotListController_refresh
      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: Reload external bot-feeds now (BOT_FEED_URLS) into the in-memory matcher.
      tags:
      - Tracking / Bot List
      x-required-scope:
      - admin:write
  /api/bot-list/cidr:
    post:
      operationId: BotListController_addCidr
      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: Add a custom bot CIDR to the GLOBAL bot-list (e.g.
      tags:
      - Tracking / Bot List
      x-required-scope:
      - admin:write
    delete:
      operationId: BotListController_removeCidr
      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: ''
      security:
      - jwt: []
      summary: Remove a custom bot CIDR from the GLOBAL bot-list. SUPER-only
      tags:
      - Tracking / Bot List
      x-required-scope:
      - admin:write
  /api/bot-list/ua:
    post:
      operationId: BotListController_addUa
      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: Add a custom bot User-Agent regex to the GLOBAL bot-list (e.g.
      tags:
      - Tracking / Bot List
      x-required-scope:
      - admin:write
    delete:
      operationId: BotListController_removeUa
      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: ''
      security:
      - jwt: []
      summary: Remove a custom bot User-Agent regex from the GLOBAL bot-list. SUPER-only
      tags:
      - Tracking / Bot List
      x-required-scope:
      - admin:write
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.