Mapp Marketing Cloud Related Data API

The Related Data API from Mapp Marketing Cloud — 4 operation(s) for related data.

Documentation GitHub OpenAPI

Operations 4

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 /relatedData/createRecord Add a record to a related data set · Create a related data record #

Ask an LLM

“How do I add one row of data to a related data set for a contact?”

“What must a new related data record include?”

Tell an agent

Add a record to the products data set for key test-user@example.com.

Insert one new related data row with these column values.

POST /relatedData/deleteRecords Delete related data records · Delete related data records #

Ask an LLM

“Can I delete only the related data rows that match a filter?”

“How do I remove a customer's records from a related data set?”

Tell an agent destructive · confirm first

Delete the products records for testuser@domain.com where bicycle is 14.

Remove all related data records under this key.

GET /relatedData/getRecordsByKey Get related data records for a key · Get related data records by key #

Ask an LLM

“What related data rows are stored for a particular customer?”

“Can I read every record under one key in a data set?”

Tell an agent

Get all records in data set {datasetName} for key {key}.

Show the {datasetName} rows stored for {key}.

POST /relatedData/updateRecords Update related data records for a key · Update related data records #

Ask an LLM

“Does updating related data without a filter delete and re-add all rows for the key?”

“Can I change the unique column of a related data record?”

Tell an agent

Update the products records for this key with new values.

Replace all related data rows for this customer with these.

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-related-data-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

openapi: 3.2.0
info:
  title: Mapp Engage public Related Data 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: Related Data
paths:
  /relatedData/createRecord:
    post:
      tags:
      - Related Data
      summary: Create a related data record
      description: 'Adds ONE record to a data set. The data to insert is defined in a JSON block submitted in the request body.

        The JSON block must contain the dataset''s name, the key value, and a data array of name and value elements. The name references the column in the related data set, and the value contains the data to be inserted into the corresponding columns.


        datasetName (String, required) - Name of the related data set. All related data records reside within a data set identified by a unique name.

        key (String, required) - Key defining which record(s) to select from the data set.

        data (Attribute, optional) - An optional list of name, value pair.

        Request body example:


        {

        "datasetName": "products",

        "key": "testuser@domain.com",

        "data": [

        {

        "name": "productname",

        "value": "bicycle"

        },

        {

        "name": "quantity",

        "value": "1"

        }

        ]

        }'
      operationId: createRecord
      responses:
        '200':
          description: ''
        '400':
          description: RelatedDataList with dataSetName=products does not exist.
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RelatedDataRecord'
  /relatedData/deleteRecords:
    post:
      tags:
      - Related Data
      summary: Delete related data records
      description: 'Delete a record in a related data set.

        Request body example:


        {"datasetName": "products",

        "key": "testuser@domain.com",

        "filter":

        [{

        "name":"bicycle",

        "value":"14"

        }]

        }'
      operationId: deleteRecords
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: integer
                format: int64
            application/xml:
              schema:
                type: integer
                format: int64
        '400':
          description: ''
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RelatedDataFilter'
  /relatedData/getRecordsByKey:
    get:
      tags:
      - Related Data
      summary: Get related data records by key
      description: 'Returns all related data records stored under the specified key in a related data set.


        Response body example - 1 record:


        [

        {

        "datasetName": "products",

        "key": "test-user@example.com",

        "data": [

        { "name": "hairColor", "value": "green" },

        { "name": "eyeColor", "value": "blue" }

        ]

        }

        ]


        Response body example - empty result:


        []'
      operationId: getRecordsByKey
      parameters:
      - name: datasetName
        in: query
        description: Name of the related data set
        required: true
        schema:
          type: string
      - name: key
        in: query
        description: Key defining which record(s) to select from the data set
        required: true
        schema:
          type: string
      responses:
        '200':
          description: successful operation
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/RelatedDataRecord'
        '400':
          description: ''
  /relatedData/updateRecords:
    post:
      tags:
      - Related Data
      summary: Update related data records
      description: 'Updates all or specific records for a key in a related data set. For the requests without filter, the behavior is the same as in file import ("delete all + add").


        There is no possibility to update the unique RD column. The unique column is treated as a part of the key that''s why to change such entities it needs to be deleted and created as the new row.

        Request body example:


        {

        "datasetName": "products",

        "key": "testuser@domain.com",

        "data": [

        {

        "name": "quantity",

        "value": "14"

        }

        ]

        ,

        "filter": [{

        "name": "bicycle",

        "value": "1"

        }]

        }'
      operationId: updateRecords
      responses:
        '200':
          description: Successful response - number of deleted previous occurrences for the specified key. One record was added
          content:
            application/json:
              schema:
                type: integer
                format: int64
            application/xml:
              schema:
                type: integer
                format: int64
        '400':
          description: ''
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RelatedDataRecordAndFilter'
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

Mapp Marketing Cloud Related Data API

Operations 4

Documentation

Specifications

Other Resources

Work with this as data

MCP server

Tools for apis

Call it yourself

Get an API key

OpenAPI Specification