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
SAP Emarsys

SAP Emarsys Segments API

In this batch you may find endpoints related to segments. Published by SAP Emarsys as a Swagger 2.0 document with 11 operation(s). Part of the SAP Emarsys Core API. Authentication is the legacy X-WSSE UsernameToken header, which SAP Emarsys has deprecated with a final sunset at the end of 2026 in favour of OAuth 2.0 / OpenID Connect on the v3 surface. Errors are returned as a proprietary replyCode/replyText/data envelope and can appear inside HTTP 200 responses, so callers must inspect replyCode rather than the status code.

Documentation Provider Profile APIs.io OpenAPI GitHub

SAP Emarsys Segments API is one of 25 APIs that SAP Emarsys publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Segmentation, Audience, and Filters. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 11 operations across 10 paths, and defines 1 schema. It is described by OpenAPI 2.0, at version v2.

Requests are made against the base URL https://api.emarsys.net/api.

11 operations 10 paths 1 schemas 7 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
v2
Base URL
https://api.emarsys.net/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

SAP Emarsys Segments API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-WSSE (X-WSSE).

Paths & Operations 11

Across 10 paths, the API surfaces 11 operations — 7 GET, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Operations 11
PUT
/v2/filter
Create a Segment
createSegment 1 param → 200400
GET
/v2/filter/{segmentId}
List Segments
listSegments 1 param → 200400
PUT
/v2/filter/{segmentId}/contact_criteria
Update Contact Criteria in a Segment
updateContactCriteriaInSegment 2 params → 200400404
GET
/v2/filter/{segmentId}/contact_criteria
Get Segment Contact Criteria
getSegmentContactCriteria 1 param → 200400404
GET
/v2/filter/{segmentId}/delete
Delete a Segment
deleteSegment 1 param → 200400404
GET
/v2/filter/{segmentId}/contacts/count
Count Contacts in a Segment
countContactsInSegment 1 param → 200400
GET
/v2/filter/{segmentId}/contacts/{contactId}
Look Up a Contact in a Segment
lookUpContactInSegment 2 params → 200400
POST
/v2/filter/{segmentId}/single_runs
Run a Segment for a Single Contact
runContactSegmentSingle 2 params → 200400404
GET
/v2/filter/single_runs/{runId}
Poll the Status of a Segment Run for a Single Contact
pollStatusContactSegmentSingle 1 param → 200404
POST
/v2/filter/{segmentId}/runs
Run a Segment for Multiple Contacts
runContactSegmentBatch 1 param → 200404
GET
/v2/filter/runs/{runId}
Poll the Status of a Segment Run for Multiple Contacts
pollStatusContactSegmentBatch 1 param → 200404

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is default-response (3 properties). Each schema is shown below with its type and property counts.

default-response
object
See the following documents for details on the error codes: - [HTTP 200 errors](docs/response-codes/http-200-responses.md) - [HTTP 400 errors](docs/response-co…
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emarsys-segments-openapi.yml Raw ↑

Other APIs SAP Emarsys publishes across the network.

SAP Emarsys Accounts API
AE Profile APIs.io
SAP Emarsys Auto-import Profiles API
AE Profile APIs.io
SAP Emarsys Bulk Response Summary API
AE Profile APIs.io
SAP Emarsys Conditional Text Rules API
AE Profile APIs.io
SAP Emarsys Contact and Email Data API
AE Profile APIs.io
SAP Emarsys Contact Lists API
AE Profile APIs.io
SAP Emarsys Contact Sources API
AE Profile APIs.io
SAP Emarsys Contacts API
AE Profile APIs.io
SAP Emarsys Email Campaign Lifecycle API
AE Profile APIs.io
SAP Emarsys Email Campaigns API
AE Profile APIs.io
SAP Emarsys Email Reporting API
AE Profile APIs.io
SAP Emarsys Email Templates API
AE Profile APIs.io
#Segmentation#Audience#Filters
← Back to S APIs
API Details
ID
emarsys:emarsys-segments-api
Base URL
https://api.emarsys.net/api
Docs
https://dev.emarsys.com/docs/core-api-reference/ehr0tded4ctcw-emarsys-core-api-segments-endpoint-batch
Provider
SAP Emarsys
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=emarsys-segments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/emarsys-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 SAP Emarsys 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.