---
title: "Engage API"
slug: "engage-api"
status: "update"
updated: 2026-07-31T08:01:12Z
published: 2026-07-31T08:01:27Z
canonical: "docs.mapp.com/engage-api"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Engage API

The Mapp Engage API lets you exchange data between your systems and Mapp Engage — send messages, create and update contacts, manage groups and segments, trigger automations, and more.

## Interfaces

- **REST API (REST 2.0)** — the current interface; use this for all new integrations.
- **SOAP API** and **Control XML** — legacy interfaces, kept for existing integrations and large-volume data transfers.

## API versions

Three terms appear across this documentation:

- **REST 2.0** — the current generation of the Engage REST API. New integrations should target REST 2.0.
- **v19** — the current incremental version within REST 2.0. Versions are additive: every prior version (v1–v19) keeps all earlier operations and only adds new ones. You can pin a version in the URL (e.g. `/api/rest/v19/...`).
- **API 1** — a separate, earlier generation, still in production for some workflows. It is not an old version of REST 2.0.

To check which version your tenant currently exposes, call `GET /system/getApiVersion`.

## Getting started

See [Getting Started](/v1-api/apidocs/getting-started-with-engage-api) for authentication, base URL, and required headers. Browse [Endpoints](/v1-api/apidocs/engage-api-calls) for the full method reference and [Objects & Types](/v1-api/apidocs/rest-api-objects-types) for the data structures. For ready-made examples, see [Use Cases](/v1-api/apidocs/use-cases-engage-api).