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

MoEngage Flows API

The Flows API from MoEngage — 4 operation(s) for flows.

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

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

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

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

4 operations 4 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
5.0
Base URL
https://api-01.moengage.com/v1
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

MoEngage Flows 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 4 paths, the API surfaces 4 operations — 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Flows 4
POST
/v5/flows/search
Search Flows
searchFlows 2 params body → 200400401403429500
GET
/v5/flows/{flow_id}
Get a Single Flow
getFlow 4 params → 200400401403404429500
GET
/v5/flows/{flow_id}/versions/{version_id}
Get a Specific Version of a Flow
getFlowVersion 4 params → 200400401403404429500
PATCH
/v5/flows/{flow_id}/status
Update Flow Status
updateFlowStatus 4 params body → 200400401403404409429500

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are FlowSearchRequest (12 properties), FlowSummary (11 properties), FlowNode (7 properties), ConversionGoalDetails (6 properties). Each schema is shown below with its type and property counts.

ConversionGoalDetails
objectnull
Conversion-goal configuration from the entry node. Null when the flow has no conversion goal.
6 properties
FlowStatusEnum
string
Public lifecycle status of a flow (or of a specific version), independent of the archived flag.
FlowSearchRequest
object
Filters for listing flows. All filters are optional and combine with AND. Enum filters (status, deliverytype) are case-insensitive.
12 properties
FlowSettings
object
Flow-level settings. Null-valued fields may be omitted.
5 properties
FlowNode
object
One stage of the flow, such as a trigger, an action, a wait, a condition, or a split.
7 properties 1 required
FlowSummary
object
One flow as it appears in a search or list result.
11 properties 1 required
FlowVersion
object
One version of a flow, as listed in a detail response's versions.
4 properties
FlowSearchResponse
object
3 properties 3 required
FlowDetailData
FlowStatusRequest
object
4 properties 2 required
DeliveryTypeEnum
string
Indicates how users enter the flow.
FlowAttribution
objectnull
Click and impression attribution windows for the flow, derived from its channel action nodes. Null when no channel action declares them.
2 properties
FlowDetailResponse
object
3 properties 3 required
ErrorResponse
object
2 properties 2 required
FlowStatusResponse
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

moengage-flows-api-openapi.yml Raw ↑

Other APIs MoEngage publishes across the network.

MoEngage MCP Server
MoEngage Bulk API
MoEngage Business Events API
MoEngage Campaign Reports API
MoEngage Cards API
MoEngage Catalog API
MoEngage Cohort Sync API
MoEngage Content Blocks API
MoEngage Coupon Files API
MoEngage Coupon Lists API
MoEngage Create Campaigns API
MoEngage Dashboards API
Where this information came from

This is an independent, third-party profile of MoEngage Flows 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.