---
title: Request Requirements
slug: engine-api/request-requirements
description: How to send POST requests to the Monetate Engine API
image:  https://archbee-image-uploads.s3.amazonaws.com/ceIfEvQHzQk1IVxoRWUh7/K9eTL4jKm7UQINb6zNziJ-20250912-181225.png
docTags: 
createdAt: 2024-06-14T19:50:48.231Z
---

When an Engine API request is made, Monetate's decision engine evaluates all active [Omnichannel experiences](https://docs.monetate.com/docs/create-an-omnichannel-experience) in the account and uses the provided context to make decisions about which experiences and actions for which the customer has qualified.

All Engine API requests must be made via a [POST to the decision endpoint](docId\:lQST4ABe9zqX_k3ta8Nnh) and include the following:

- Content-type header
- Body

## Endpoint

The endpoint for Engine API requests is as follows:

:::CodeblockTabs
Engine API Endpoint

```none
https://engine.monetate.net/api/engine/v1/decide/{retailerShortname}
```
:::

The `{retailerShortname}` placeholder is a unique identifier that specifies the parent value of the account. This identifier is provided by your dedicated Services team. You can also find it on the **API** tab of the [Integration page](https://docs.monetate.com/docs/integration-tools#api) of the Monetate platform settings.

A subsequent `channel` key-value pair is required in the request body that specifies the account, domain, and instance (for example, `"channel": "a-887f2483/p/example.com"`).

## Content-Type Header

The content-type header is required and may be set to either `application/JSON` or `text/plain`.

Monetate recommends `text/plain` to avoid an extra round trip (the CORS preflight OPTIONS request associated with `application/JSON`).

## Body

The [body](docId\:lQST4ABe9zqX_k3ta8Nnh) of an Engine API request consists of JSON that identifies the account and passes page- and user-level data via events.

## Events in a Request

Each of the three event types instructs the Engine API to do different things with the associated information:

- Event types that begin with `monetate:decision` request that the Engine API evaluate active experiences and return actions
- Event types that begin with `monetate:context` provide information about the visitor or page that Monetate uses for targeting and decision-making purposes
- Event types that begin with `monetate:record` provide information that Monetate should record but that isn't used for targeting or decision-making purposes

All Engine API requests should follow the same structure as noted in the [API reference](docId\:lQST4ABe9zqX_k3ta8Nnh). However, including various API models depends on individual integrations and use cases.

- Include the `pageType` parameter within the [monetate\:context\:PageView](docId:0S1UVO4ctyzDYZRpvevDN) event to use corresponding action conditions
- Include the [monetate\:context\:UserAgent](docId\:NgmNvrdCuYtMtLDLgUyYR) event and the end user's `userAgent`  [value](docId:9cG-LczaQTIAFlsWBJpB2) as context for analytics so that stealth sessions are registered properly
- Include the [monetate\:context\:ProductThumbnailView](docId:9VI5lbVf0klH3Qj6Xa2-E) event to communicate all items present on a listing page or search results page, which can then be used for [action conditions](docId\:N-VumBACFtG0JlhtIkean) or advanced [Product Recommendations](https://docs.monetate.com/docs/recommendations) use cases
- Include the [monetate\:context\:ProductDetailView](docId:0QyZqPaP6DHh9e-BNP6iY) event to communicate a product view has occurred and subsequently target/condition based on a specific product, brand, product type/category, or advanced Product Recommendations use cases
- Include the [monetate\:context\:Cart](docId\:CCLZbgZdAjWM9HubH3fBi) event to communicate cart contents which are used for behavioral analytics and cart-content targets or action conditions
- Include the [monetate\:context\:Purchase](docId:1WbW8Jiq4stq8KCOrSh2n) event to communicate a purchase has occurred for behavioral analytics and purchase

See [Target, Event, & Condition Mapping](docId\:N-VumBACFtG0JlhtIkean) for more extensive mapping of Engine API models and how you can use them for targeting and action conditions in experiences and actions.