Mapp Marketing Cloud

Mapp Marketing Cloud Process API

The Process API from Mapp Marketing Cloud — 3 operation(s) for process.

GitHub OpenAPI

Operations 3

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 /process/applyAction Change the status of a process · Apply an action to a process #
Ask an LLM
“Can I pause or resume a running process?”
“Which call changes an existing process's status?”
Tell an agent
Apply a pause action to process {processId}.
Change the status of process {processId}.
GET /process/getDetails Get details of a process · Get process details #
Ask an LLM
“What's the current state of a particular process?”
“Can I look up one process by its ID?”
Tell an agent
Get details for process {processId}.
Show what process {processId} is doing.
GET /process/getProcessList List processes · List processes #
Ask an LLM
“Which processes have failed recently?”
“How many processes can I list per page?”
Tell an agent
List processes with status {status}.
Show {limit} processes starting at offset {offset}.

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://artifacts.apis.io/mapp/openapi/mapp-process-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-process-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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-process-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Mapp Engage public Process 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: Process
paths:
  /process/applyAction:
    post:
      tags:
      - Process
      summary: Apply an action to a process
      description: Changes the status of an existing process.
      operationId: applyAction
      parameters:
      - name: processId
        in: query
        description: Process identifier
        required: true
        schema:
          type: integer
          format: int64
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: string
                enum:
                - FAILED
                - FINISHED
                - PAUSED
                - PROCESSING
            application/xml:
              schema:
                type: string
                enum:
                - FAILED
                - FINISHED
                - PAUSED
                - PROCESSING
        '400':
          description: ''
      requestBody:
        content:
          application/json:
            schema:
              type: string
  /process/getDetails:
    get:
      tags:
      - Process
      summary: Get process details
      description: Returns information for the process identified by the specified process ID.
      operationId: getProcessDetails
      parameters:
      - name: processId
        in: query
        description: Process identifier
        required: true
        schema:
          type: integer
          format: int64
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ProcessDetails'
            application/xml:
              schema:
                $ref: '#/components/schemas/ProcessDetails'
        '400':
          description: ''
  /process/getProcessList:
    get:
      tags:
      - Process
      summary: List processes
      description: Returns a paginated list of processes, optionally filtered by status. Results are ordered by start date descending. Use 'limit' and 'offset' to page through results.
      operationId: getProcessList
      parameters:
      - name: status
        in: query
        description: 'Optional status filter: PROCESSING, PAUSED, FINISHED, or FAILED'
        required: false
        schema:
          type: string
      - name: limit
        in: query
        description: Maximum number of processes to return. Default 500, max 500.
        required: false
        schema:
          type: integer
          format: int64
      - name: offset
        in: query
        description: Number of processes to skip. Default 0.
        required: false
        schema:
          type: integer
          format: int64
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: array
                items:
                  type: object
            application/xml:
              schema:
                type: array
                items:
                  type: object
        '400':
          description: ''
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