✨ MoEngage NEXT Spring 2026 — The Future of Engagement is Agentic. Join us on April 28. Register now
curl --request PATCH \
--url https://api-{dc}.moengage.com/v2/custom-segments/unarchive \
--header 'Authorization: Basic <encoded-value>' \
--header 'Content-Type: application/json' \
--data '
{
"name": "custom_segment_unique_name"
}
'{
"message": "Successfully unarchived the custom segment",
"success": true,
"cs_name": "custom_segment_unique_name"
}This API unarchives an existing segment, making it active again.
curl --request PATCH \
--url https://api-{dc}.moengage.com/v2/custom-segments/unarchive \
--header 'Authorization: Basic <encoded-value>' \
--header 'Content-Type: application/json' \
--data '
{
"name": "custom_segment_unique_name"
}
'{
"message": "Successfully unarchived the custom segment",
"success": true,
"cs_name": "custom_segment_unique_name"
}Documentation Index
Fetch the complete documentation index at: https://moengage-ios-release-notes-breaking-changes-doc-1961.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Authentication is done via Basic Auth. This requires a base64-encoded string of your credentials in the format 'username:password'.
For more information on authentication and getting your credentials, refer here.
The name of the segment to be unarchived.
Was this page helpful?