Mapp Marketing Cloud

Mapp Marketing Cloud Blacklist API

The Blacklist API from Mapp Marketing Cloud — 6 operation(s) for blacklist.

GitHub OpenAPI

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

POST /blacklist/createGroupEntries Block addresses for one group · Create group blacklist entries #
Ask an LLM
“How do I stop an email address or domain from receiving mail from one group?”
“Can I block a mobile number for a single group only?”
Tell an agent
Add test@test.com to the blacklist for group {groupId}.
Block this email domain in group {groupId}.
POST /blacklist/createGroupEntriesHashed Block hashed emails for one group · Create hashed group blacklist entries #
Ask an LLM
“Can I blacklist emails for a group using MD5 hashes instead of plain addresses?”
“How do I add hashed entries to a group blacklist?”
Tell an agent
Add these MD5-hashed emails to the blacklist for group {groupId} with hashed set to {hashed}.
Block hashed address 6a4b6cb2045fd55f706eaebd6ab5d4f7 in group {groupId}.
POST /blacklist/createSystemEntriesHashed Block hashed entries system-wide · Create hashed system blacklist entries #
Ask an LLM
“Can I add MD5-hashed emails or app aliases to the system-wide blacklist?”
“What types can go on the system blacklist in hashed form?”
Tell an agent
Add these hashed emails to the system blacklist with hashed set to {hashed}.
Block hashed address 0dbfb46341bc3d195db23e4015b20847 across the whole system.
POST /blacklist/createSystemEntries Block addresses system-wide · Create system blacklist entries #
Ask an LLM
“How do I block an email, domain or phone number from every group at once?”
“Can I add a plain phone number to the Mapp Engage system blacklist?”
Tell an agent
Add test@test.com to the system blacklist.
Block phone number 336789012345 system-wide.
POST /blacklist/deleteGroupEntries Unblock addresses for one group · Delete group blacklist entries #
Ask an LLM
“How do I remove an email from a group's blacklist so they can get mail again?”
“Can I lift a group-level block on a domain?”
Tell an agent destructive · confirm first
Remove test@test.com from the blacklist for group {groupId}.
Unblock this domain in group {groupId}.
POST /blacklist/deleteSystemEntries Unblock addresses system-wide · Delete system blacklist entries #
Ask an LLM
“Can I take an address off the system-wide blacklist?”
“Which call deletes system blacklist entries for phone numbers?”
Tell an agent destructive · confirm first
Remove test@test.com from the system blacklist.
Lift the system-wide block on phone number 336789012345.

Documentation

📖
Documentation
https://docs.mapp.com/apidocs/engage-api
📖
GettingStarted
https://docs.mapp.com/apidocs/getting-started-with-engage-api
📖
APIReference
https://docs.mapp.com/apidocs/engage-api-calls
📖
Documentation
https://docs.mapp.com/apidocs/analytics-api
📖
APIReference
https://docs.mapp.com/apidocs/analysis-analytics-api
📖
Documentation
https://docs.mapp.com/apidocs/product-catalog-api
📖
APIReference
https://docs.mapp.com/apidocs/product-catalog-api-api-reference
📖
Authentication
https://docs.mapp.com/apidocs/product-catalog-api-authentification
📖
Documentation
https://docs.mapp.com/apidocs/mapp-fashion-api-documentation

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/mapp/refs/heads/main/openapi/mapp-blacklist-api-openapi.yml

Other Resources

🔗
Postman
https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/Analytics%20API.postman_collection.json
🔗
ChangeLog
https://docs.mapp.com/apidocs/changelog-mapp-fashion-api

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/mapp:mapp-blacklist-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

mapp-blacklist-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Mapp Engage public Blacklist API
  version: '1'
  description: 'Mapp Engage REST API (REST 2.0, incremental version v19). Assembled verbatim from the per-operation OpenAPI fragments Mapp publishes on each endpoint page of https://docs.mapp.com/apidocs/. The base URL is tenant-specific: take your Mapp Engage login host and append /api/rest/v19.'
  contact:
    name: Mapp Technical Support
    url: https://mapp.com/tech-support/
servers:
- url: /api/rest/v19
security:
- basicAuth: []
tags:
- name: Blacklist
paths:
  /blacklist/createGroupEntries:
    post:
      tags:
      - Blacklist
      summary: Create group blacklist entries
      description: 'Adds new entries (email, emailDomain or mobileNumber) to the group blacklist.

        Request body example:


        [{

        "type": "EMAIL",

        "pattern": "test@test.com"

        }]'
      operationId: createGroupEntries
      parameters:
      - name: groupId
        in: query
        description: ID of the group
        required: true
        schema:
          type: integer
          format: int64
      responses:
        '200':
          description: 'Example response: <br><br>[{<br>    "success": true,<br>    "id": "test@test.com",<br>    "errorActor": null,<br>    "errorCode": null,<br>    "errorMessage": null<br>}]'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateResult'
            application/xml:
              schema:
                $ref: '#/components/schemas/CreateResult'
        '400':
          description: ''
      requestBody:
        content:
          application/json:
            schema:
              type: array
              items:
                $ref: '#/components/schemas/BlacklistEntry'
  /blacklist/createGroupEntriesHashed:
    post:
      tags:
      - Blacklist
      summary: Create hashed group blacklist entries
      description: 'Adds new hashed email entries to the group blacklist. Entries can be hashed using md5hashgenerator.

        Request body example:


        [

        {

        "type": "EMAIL",

        "pattern":"6a4b6cb2045fd55f706eaebd6ab5d4f7"

        },

        {

        "type": "EMAIL",

        "pattern":"0dbfb46341bc3d195db23e4015b20847"

        }

        ]'
      operationId: createGroupEntriesHashed
      parameters:
      - name: groupId
        in: query
        description: The group ID.
        required: true
        schema:
          type: integer
          format: int64
      - name: hashed
        in: query
        description: Hashing algorithm used to hash given entries. Either 'clear-text' or 'md5'
        required: true
        schema:
          type: string
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateResult'
            application/xml:
              schema:
                $ref: '#/components/schemas/CreateResult'
        '400':
          description: ''
      requestBody:
        content:
          application/json:
            schema:
              type: array
              items:
                $ref: '#/components/schemas/BlacklistEntry'
  /blacklist/createSystemEntriesHashed:
    post:
      tags:
      - Blacklist
      summary: Create hashed system blacklist entries
      description: 'Adds new entries (email, email domain, mobile number, or mobile app alias) to the system blacklist. Entries can be hashed using md5hashgenerator.

        Request body example:


        [

        {

        "type": "EMAIL",

        "pattern":"6a4b6cb2045fd55f706eaebd6ab5d4f7"

        },

        {

        "type": "EMAIL",

        "pattern":"0dbfb46341bc3d195db23e4015b20847"

        }

        ]'
      operationId: createSystemEntriesHashed
      parameters:
      - name: hashed
        in: query
        description: the hashing algorithm used to hash given entries. Either 'clear-text' or 'md5'
        required: true
        schema:
          type: string
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateResult'
            application/xml:
              schema:
                $ref: '#/components/schemas/CreateResult'
        '400':
          description: ''
      requestBody:
        content:
          application/json:
            schema:
              type: array
              items:
                $ref: '#/components/schemas/BlacklistEntry'
  /blacklist/createSystemEntries:
    post:
      tags:
      - Blacklist
      summary: Create system blacklist entries
      description: 'Adds new entries (email, email domain or mobile number) to the system blacklist.

        Request body examples:


        [{

        "type": "EMAIL",

        "pattern": "test@test.com"

        }]


        [{

        "type": "PHONE_NUMBER",

        "pattern": "336789012345"

        }]'
      operationId: createSystemEntries
      responses:
        '200':
          description: 'Example response: <br><br>[{<br>    "success": true,<br>    "id": "test@test.com",<br>    "errorActor": null,<br>    "errorCode": null,<br>    "errorMessage": null<br>}]'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateResult'
            application/xml:
              schema:
                $ref: '#/components/schemas/CreateResult'
        '400':
          description: ''
      requestBody:
        content:
          application/json:
            schema:
              type: array
              items:
                $ref: '#/components/schemas/BlacklistEntry'
  /blacklist/deleteGroupEntries:
    post:
      tags:
      - Blacklist
      summary: Delete group blacklist entries
      description: 'Deletes entries (email, email domain or mobile number) from the group blacklist.

        Request body example:


        [{

        "type": "EMAIL",

        "pattern": "test@test.com"

        }]'
      operationId: deleteGroupEntries
      parameters:
      - name: groupId
        in: query
        description: ID of the group.
        required: true
        schema:
          type: integer
          format: int64
      responses:
        '200':
          description: 'Example response: <br><br>[{<br>    "success": true,<br>    "id": "test@test.com",<br>    "errorActor": null,<br>    "errorCode": null,<br>    "errorMessage": null<br>}]'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateResult'
            application/xml:
              schema:
                $ref: '#/components/schemas/CreateResult'
        '400':
          description: ''
      requestBody:
        content:
          application/json:
            schema:
              type: array
              items:
                $ref: '#/components/schemas/BlacklistEntry'
  /blacklist/deleteSystemEntries:
    post:
      tags:
      - Blacklist
      summary: Delete system blacklist entries
      description: 'Deletes entries (email, email domain or mobile number ) from the system blacklist.

        Request body example:


        [{

        "type": "EMAIL",

        "pattern": "test@test.com"

        }]'
      operationId: deleteSystemEntries
      responses:
        '200':
          description: 'Example response: <br><br>[{<br>    "success": true,<br>    "id": "test@test.com",<br>    "errorActor": null,<br>    "errorCode": null,<br>    "errorMessage": null<br>}]'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateResult'
            application/xml:
              schema:
                $ref: '#/components/schemas/CreateResult'
        '400':
          description: ''
      requestBody:
        content:
          application/json:
            schema:
              type: array
              items:
                $ref: '#/components/schemas/BlacklistEntry'
components:
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic
      description: HTTP Basic authentication with a Mapp Engage system user of type API (or Hybrid).
x-apievangelist-provenance:
  method: searched
  generated: '2026-08-12'
  source: https://docs.mapp.com/apidocs/ (per-endpoint OpenAPI fragments)
  note: Union of the OpenAPI JSON fragments Mapp publishes on each endpoint page. Mapp does not serve one consolidated document at a public URL; the tenant-served Swagger lives at https://<your-engage-host>/apidoc/swagger.json and requires a tenant. Operation bodies, parameters, responses, tags, summaries and descriptions are verbatim from Mapp. The swagger/basePath/schemes/securityDefinitions envelope is added by API Evangelist from the published Getting Started guide; no operation content was authored.
  duplicate_operation_ids_suffixed: 30