How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
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.

Documentation Provider Profile APIs.io OpenAPI GitHub

MoEngage Filter Segments API is one of 46 APIs that MoEngage publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Filter Segments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 2 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 3.0.

Requests are made against a single base URL, https://api-{dc}.moengage.com.

4 operations 2 paths 15 schemas 2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0
Base URL
https://api-01.moengage.com/v1
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

MoEngage Filter Segments API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — Authentication is done via Basic Auth. This requires a base64-encoded string of your credentials in the format 'username:password'. - Username: Use your MoEnga…

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Filter Segments 4

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. W…

GET
/v3/custom-segments
List Segments
listCustomSegments 2 params → 200400401429500
POST
/v3/custom-segments
Create Filter Segment
createFilterSegment 1 param body → 201400401409413429500
GET
/v3/custom-segments/{id}
Get Segment by ID
getCustomSegment 2 params → 200400401429500
PATCH
/v3/custom-segments/{id}
Update Filter Segment
updateFilterSegment 2 params body → 200400401403404409412413

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are FilterSegmentDataV3 (8 properties), AttributeFilterV3 (8 properties), ActionFilterV3 (6 properties), ErrorDataV3 (6 properties). Each schema is shown below with its type and property counts.

FilterSegmentUpdateRequestV3
object
Request schema for updating an existing filter-based segment.
3 properties 1 required
SegmentListResponseV3
object
Response schema for listing segments.
3 properties
FilterSegmentResponseV3
object
Response schema for filter segment operations (create/update).
3 properties
SegmentListItemV3
object
Summary information about a segment in a list.
5 properties
AttributeFilterV3
object
A filter based on a user or event attribute. Allowed Operators per Data Type: bool: is, exists double: in, between, lessThan, greaterThan, exists string: in, c…
8 properties 4 required
ServerErrorDataV3
object
Error details for server errors (5xx).
2 properties 2 required
FilterSegmentRequestV3
object
Request schema for creating a filter-based segment.
2 properties 2 required
ServerErrorResponseV3
object
Error response schema for server errors (5xx).
3 properties
FilterSegmentDataV3
object
Detailed information about a segment.
8 properties
FilterV3
A single filter criterion, which can be user attribute-based or action-based.
ErrorDataV3
object
Error details for client errors (4xx).
6 properties 2 required
ErrorResponseV3
object
Error response schema for client errors (4xx).
3 properties
ActionAttributeFilterGroupV3
object
A logical grouping of attribute filters for action-based filtering.
2 properties 2 required
ActionFilterV3
object
A filter based on a user action (event).
6 properties 5 required
FilterGroupV3
object
A logical grouping of filters.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

moengage-filter-segments-api-openapi.yml Raw ↑

Other APIs MoEngage publishes across the network.

MoEngage MCP Server
AE Profile APIs.io
MoEngage Bulk API
AE Profile APIs.io
MoEngage Business Events API
AE Profile APIs.io
MoEngage Campaign Reports API
AE Profile APIs.io
MoEngage Cards API
AE Profile APIs.io
MoEngage Catalog API
AE Profile APIs.io
MoEngage Cohort Sync API
AE Profile APIs.io
MoEngage Content Blocks API
AE Profile APIs.io
MoEngage Coupon Files API
AE Profile APIs.io
MoEngage Coupon Lists API
AE Profile APIs.io
MoEngage Create Campaigns API
AE Profile APIs.io
MoEngage Dashboards API
AE Profile APIs.io
#Filter Segments
← Back to M APIs
API Details
ID
moengage:moengage-filter-segments-api
Base URL
https://api-01.moengage.com/v1
Docs
https://www.moengage.com/docs/api/data/data-overview
Provider
MoEngage
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=moengage-filter-segments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/moengage-filter-segments-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of MoEngage Filter Segments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.