---
title: Getting Started with the Engine API
slug: engine-api
description: Introduction to Monetate's Engine API
image:  https://archbee-image-uploads.s3.amazonaws.com/ceIfEvQHzQk1IVxoRWUh7/K9eTL4jKm7UQINb6zNziJ-20250912-181225.png
docTags: 
createdAt: 2024-06-14T19:56:25.407Z
---

Monetate's Engine API is a RESTful API that serves as a direct entry point to its decision engine and allows clients to use it in any channel: Web (server-side or within the browser), mobile applications, SPA frameworks, and nontraditional implementations such as in-store displays or SMS/text messaging.

The Engine API allows three things to be done with a single call:

- Send contextual information about the current visitor/page.
- Retrieve actions that are supposed to fire in the current context. These actions can be part of any Omnichannel experience in Monetate and can be a mix of personalized content and tests to be activated.
- Send events/metrics to Monetate to measure success.

Bundling all these capabilities into a single endpoint allows all data to be received via a single call and reduces latency when transmitting to Monetate.

## Implementation Checklist

Use this worksheet to keep track of your progress while you implement Monetate Engine API on your site.

- [ ] Hold planning meeting with all stakeholders.
- [ ] Agree on the implementation approach.
- [ ] Create a roadmap of ideas to understand which experiences should be Engine API vs  [Monetate tag](docId\:zcx_p3d6ND2Rr5bJLOyUG), if using a [hybrid](docId\:ZFxS45Ymf6aIcWwKKgXcC) approach, to help the teams with prioritizing builds.
- [ ] Request [Omnichannel action templates](https://docs.monetate.com/docs/omnichannel-experiences-available-action-types).