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
MEF

MEF Trouble Ticket and Incident Notification (Mef Lso Cantata Trouble Ticket Notification)

MEF Trouble Ticket and Incident Notification from MEF — 7 path(s) described in OpenAPI.

Documentation Provider Profile APIs.io OpenAPI GitHub

MEF Trouble Ticket and Incident Notification (Mef Lso Cantata Trouble Ticket Notification) is one of 95 APIs that MEF publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 7 operations across 7 paths, and defines 22 schemas. It is described by OpenAPI 3.0.1, at version 5.0.0.

Requests are made against a single base URL, https://{serverBase}/mefApi/cantata/troubleTicketNotification/v5/.

7 operations 7 paths 22 schemas 7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
5.0.0
Base URL
https://{server}:{port}{basePath}
Resource Areas
1

Paths & Operations 7

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

Notification listeners 7

The Buyer's endpoint to send particular event types notifications to.

POST
/listener/troubleTicketAttributeValueChangeEvent
Client listener for entity TroubleTicketAttributeValueChangeEvent
listenToTroubleTicketAttributeValueChangeEvent 2 params body → 204400401403500
POST
/listener/troubleTicketStatusChangeEvent
Client listener for entity TroubleTicketStatusChangeEvent
listenToTroubleTicketStatusChangeEvent 2 params body → 204400401403500
POST
/listener/troubleTicketResolvedEvent
Client listener for entity TroubleTicketResolvedEvent
listenToTroubleTicketResolvedEvent 2 params body → 204400401403500
POST
/listener/troubleTicketInformationRequiredEvent
Client listener for entity TroubleTicketInformationRequiredEvent
listenToTroubleTicketInformationRequiredEvent 2 params body → 204400401403500
POST
/listener/incidentCreateEvent
Client listener for entity Incident Create Event
listenToIncidentCreateEvent 2 params body → 204400401403500
POST
/listener/incidentAttributeValueChangeEvent
Client listener for entity Incident Attribute Value Change Event
listenToIncidentAttributeValueChangeEvent 2 params body → 204400401403500
POST
/listener/incidentStatusChangeEvent
Client listener for entity Incident Status Change Event
listenToIncidentStatusChangeEvent 2 params body → 204400401403500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are Event (4 properties), TroubleTicketStatusChangeEventPayload (3 properties), Error (3 properties), IncidentStatusChangeEventPayload (3 properties). Each schema is shown below with its type and property counts.

Error
object
Standard Class used to describe API response error Not intended to be use directly. The code in the HTTP header is used as a discriminator for the type of erro…
3 properties 1 required
Error400
Bad Request. (https://tools.ietf.org/html/rfc7231section-6.5.1)
Error400Code
string
One of the following error codes: - missingQueryParameter: The URI is missing a required query-string parameter - missingQueryValue: The URI is missing a requi…
Error401
Unauthorized. (https://tools.ietf.org/html/rfc7235section-3.1)
Error401Code
string
One of the following error codes: - missingCredentials: No credentials provided. - invalidCredentials: Provided credentials are invalid or expired
Error403
Forbidden. (https://tools.ietf.org/html/rfc7231section-6.5.3)
Error403Code
string
This code indicates that the server understood the request but refuses to authorize it because of one of the following error codes: - accessDenied: Access deni…
Error500
Internal Server Error. (https://tools.ietf.org/html/rfc7231section-6.6.1)
Event
object
Event class is used to describe information structure used for notification.
4 properties 4 required
IncidentAttributeValueChangeEvent
IncidentCreateEvent
IncidentEventPayload
object
The identifier of the Incident being subject of this event.
2 properties 1 required
IncidentStatusChangeEvent
IncidentStatusChangeEventPayload
object
The identifier of the Trouble Ticket being subject of this event.
3 properties 2 required
IncidentStatusType
string
Possible values for the status of the Incident | status | MEF 113 name | Description | | ------------ | ------------ | ----------------------------------------…
TroubleTicketAttributeValueChangeEvent
TroubleTicketEventPayload
object
The identifier of the Trouble Ticket being subject of this event.
2 properties 1 required
TroubleTicketInformationRequiredEvent
TroubleTicketResolvedEvent
TroubleTicketStatusChangeEvent
TroubleTicketStatusChangeEventPayload
object
The identifier of the Trouble Ticket being subject of this event.
3 properties 2 required
TroubleTicketStatusType
string
Possible values for the status of the Trouble Ticket | status | MEF 113 name | Description | | ----------------------- | ---------------------- | -------------…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mef-lso-cantata-trouble-ticket-notification-openapi.yml Raw ↑

Other APIs MEF publishes across the network.

MEF LSO Interlude MEF 133.1 streaming template
AE Profile APIs.io
MEF LSO Legato Legato Service Catalog API
AE Profile APIs.io
MEF LSO Legato Legato Service Catalog Notification API
AE Profile APIs.io
MEF Alarm Management (Mef Lso Allegro Alarm Management)
AE Profile APIs.io
MEF Alarm Notification (Mef Lso Allegro Alarm Notification)
AE Profile APIs.io
MEF Fault Management (Mef Lso Allegro Fault Management)
AE Profile APIs.io
MEF Fault Management Notification (Mef Lso Allegro Fault Notification)
AE Profile APIs.io
MEF Performance Monitoring (Mef Lso Allegro Performance Monitoring)
AE Profile APIs.io
MEF Performance Monitoring Notification (Mef Lso Allegro Performance Notification)
AE Profile APIs.io
MEF Service Function Testing Notification (Mef Lso Allegro Service Function Test Notification)
AE Profile APIs.io
MEF Service Function Testing (Mef Lso Allegro Service Function Test)
AE Profile APIs.io
MEF Service Inventory Management (Mef Lso Allegro Service Inventory Management)
AE Profile APIs.io
← Back to M APIs
API Details
ID
mef:mef-lso-cantata-trouble-ticket-notification-openapi
Base URL
https://{server}:{port}{basePath}
Docs
https://github.com/MEF-GIT/MEF-LSO-Interlude-SDK/tree/kylie
Provider
MEF
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=mef-lso-cantata-trouble-ticket-notification-openapi&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mef-lso-cantata-trouble-ticket-notification-openapi"

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 MEF Trouble Ticket and Incident Notification (Mef Lso Cantata Trouble Ticket Notification), 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.