MoEngage

MoEngage Filter Segments API

If you need to create a segment based on the events or actions performed by your users on your application or website, the recommended approach is to use the filter segment API. With this API, you can create a segment by specifying the desired filter conditions. The filter segment API supports various operations, including create, update, get, and list, allowing you to effectively manage your segments based on specific criteria.

GitHub OpenAPI
Business capability
Customer Segmentation Management BC-420.20

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

GET /v3/custom-segments List user segments · List Segments #
Ask an LLM
“What custom segments exist in my MoEngage workspace?”
“Can I find a segment by its exact name?”
Tell an agent
List all my segments.
Find the segment named exactly {name}.
POST /v3/custom-segments Create a segment from filter conditions · Create Filter Segment #
Ask an LLM
“How do I create a segment of users who match a set of filters?”
“Can I define a segment by conditions instead of uploading a file?”
Tell an agent
Create filter segment {name} with filters {included_filters}.
Build a new rule-based segment called {name} using {included_filters}.
GET /v3/custom-segments/{id} Get a segment by ID · Get Segment by ID #
Ask an LLM
“How do I look up one segment's details by its ID?”
“Does fetching a segment by ID work for both file and filter segments?”
Tell an agent
Get segment {id}.
Show me the definition of segment {id}.
PATCH /v3/custom-segments/{id} Change a filter segment's conditions · Update Filter Segment #
Ask an LLM
“How do I change the filter conditions of an existing filter segment?”
“Can I rename a filter segment while updating its rules?”
Tell an agent
Update filter segment {id} to use filters {included_filters}.
Rename segment {id} to {name} with filters {included_filters}.

Documentation

📖
Documentation
https://www.moengage.com/docs/api/data/data-overview
📖
APIReference
https://www.moengage.com/docs/api/introduction
📖
Documentation
https://www.moengage.com/docs/api/campaigns/campaign-draft-overview
📖
Documentation
https://www.moengage.com/docs/api/push/push-overview
📖
Documentation
https://www.moengage.com/docs/api/custom-segments/custom-segments-overview
📖
Documentation
https://www.moengage.com/docs/api/content-blocks/content-blocks-overview
📖
Documentation
https://www.moengage.com/docs/api/catalog/catalog-overview
📖
Documentation
https://www.moengage.com/docs/api/email-subscription/email-subscription-overview
📖
Documentation
https://www.moengage.com/docs/api/analytics/analytics-overview
📖
Documentation
https://www.moengage.com/docs/api/inform/inform-overview
📖
Documentation
https://www.moengage.com/docs/api/cards/cards-overview

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/moengage/refs/heads/main/openapi/moengage-filter-segments-api-openapi.yml

Other Resources

🔗
Postman
https://www.postman.com/moengage-dev/api-docs/collection/p593wcu/moengage-data-apis
🔗
Sandbox
https://raw.githubusercontent.com/api-evangelist/moengage/refs/heads/main/sandbox/moengage-sandbox.yml

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/moengage-filter-segments-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

moengage-filter-segments-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: MoEngage Segments Filter Segments API
  description: 'Use the MoEngage Segments API to create, update, and manage your file and filter segments.


    - **v2 API:** Manage File Segments and segment lifecycle (Archive/Unarchive).

    - **v3 API:** Create, read, update, and list filter-based Segments.'
  version: '3.0'
servers:
- url: https://api-{dc}.moengage.com
  description: MoEngage API Endpoint
  variables:
    dc:
      description: The ‘dc’ in the API Endpoint URL refers to the MoEngage Data Center (DC). MoEngage hosts each customer in a different DC. You can find your DC number and replace the value of ‘dc’ in the URL by referring to the DC and API endpoint mapping [here](/api/introduction#data-centers). Your MoEngage Data Center (DC) can be 01, 02, 03, 04, 05, 06, or 101.
      default: '01'
security:
- basicAuth: []
tags:


# --- truncated at 32 KB (35 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/moengage/refs/heads/main/openapi/moengage-filter-segments-api-openapi.yml