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 Management (Mef Lso Cantata Trouble Ticket Management)

MEF Trouble Ticket and Incident Management from MEF — 9 path(s) described in OpenAPI.

Documentation Provider Profile APIs.io OpenAPI GitHub

MEF Trouble Ticket and Incident Management (Mef Lso Cantata Trouble Ticket Management) 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 12 operations across 9 paths, organized into 4 resource areas, and defines 43 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/troubleTicket/v5/.

12 operations 9 paths 43 schemas 1 DELETE5 GET1 PATCH5 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
4

Paths & Operations 12

Across 9 paths, the API surfaces 12 operations — 1 DELETE, 5 GET, 1 PATCH, 5 POST. They span 4 resource areas: troubleTicket, troubleTicket operations, incident, events subscription. Each is listed below with its method, path, parameters, and response codes.

troubleTicket 4
GET
/troubleTicket
List or found Trouble Ticket objects
listTroubleTicket 20 params → 200400401403422500
POST
/troubleTicket
Creates a TroubleTicket
createTroubleTicket 2 params body → 201400401403422500
GET
/troubleTicket/{id}
Retrieves a TroubleTicket by ID
retrieveTroubleTicket 3 params → 200400401403404500
PATCH
/troubleTicket/{id}
Updates partially a TroubleTicket
patchTroubleTicket 3 params body → 200400401403404409422500
troubleTicket operations 3
POST
/troubleTicket/{id}/cancel
Cancels a Trouble Ticket
cancelTroubleTicket 3 params → 204400401403404422500
POST
/troubleTicket/{id}/close
Closes a Trouble Ticket
closeTroubleTicket 3 params → 204400401403404422500
POST
/troubleTicket/{id}/reopen
Reopens a Trouble Ticket
reopenTroubleTicket 3 params body → 204400401403404422500
incident 2
GET
/incident
List or found Incident objects
listIncident 19 params → 200400401403422500501
GET
/incident/{id}
Retrieves ac Incident by ID
retrieveIncident 3 params → 200400401403404500501
events subscription 3
POST
/hub
Allows the Buyer to register to Trouble Ticket state change notifications
registerListener 2 params body → 201400401403422500
GET
/hub/{id}
Retrieves listener information
retrieveHub 3 params → 200400401403404500501
DELETE
/hub/{id}
Unregister a listener
unregisterListener 3 params → 204400401403404500

Schemas 43

The contract defines 43 schemas that model the data the API accepts and returns. The most detailed are FieldedAddressRepresentation (20 properties), Incident (18 properties), TroubleTicket_Find (14 properties), Incident_Find (13 properties). Each schema is shown below with its type and property counts.

AttachmentValue
object
Complements the description of an element (for instance a product) through video, pictures...
8 properties 5 required
DataSizeUnit
string
The unit of measure in the data size.
Error
object
Standard Class used to describe API response error Not intended to be used directly. The code in the HTTP header is used as a discriminator for the type of err…
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. This code indicates that the server understood the request but refuses to authorize it. (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…
Error404
Resource for the requested path not found. (https://tools.ietf.org/html/rfc7231section-6.5.4)
Error409
Conflict (https://datatracker.ietf.org/doc/html/rfc7231section-6.5.8)
Error422
Unprocessable entity due to a business validation problem. (https://tools.ietf.org/html/rfc4918section-11.2)
Error422Code
string
One of the following error codes: - missingProperty: The property the Seller has expected is not present in the payload - invalidValue: The property has an inc…
Error500
Internal Server Error. (https://tools.ietf.org/html/rfc7231section-6.6.1)
Error501
Not Implemented. Used in case Seller is not supporting an optional operation (https://tools.ietf.org/html/rfc7231section-6.6.2)
EventSubscription
object
Sets the communication endpoint address the service instance must use to deliver notification information
3 properties 2 required
EventSubscriptionInput
object
This class is used to register for Notifications. | API name | MEF 113 name | Description | | ---------------------------------------- | ---------------------…
2 properties 1 required
FieldedAddressRepresentation
object
A type of Address that has a discrete field and value for each type of boundary or identifier down to the lowest level of detail. For example "street number" i…
20 properties
Incident
object
An Incident is a record of an issue that is not part of normal operation in the Seller's network that has a possible negative impact on the operability of the…
18 properties 12 required
IncidentStatusChange
object
Holds the status notification reasons and associated date the status changed, populated by the server
3 properties
IncidentStatusType
string
Possible values for the status of the Incident | status | MEF 113 name | Description | | ------------ | ------------ | ----------------------------------------…
IncidentType
string
Possible values for the type of the Incident: - maintenance: Any scheduled or non-scheduled maintenance related Incident. - repair: Any non-scheduled Situation…
Incident_Find
object
This class represents a single list item for the response of listIncident operation.
13 properties 9 required
IssueRelationship
object
Represents relationships to other Trouble Tickets and Incidents
7 properties 6 required
MEFBuyerSellerType
string
An enumeration with buyer and seller values.
MEFByteSize
object
A size represented by value and Byte units
2 properties 2 required
MEFObservedImpactType
string
An enumeration of the possible values of impact observed by the Buyer. - degraded: When the Product is impacted and not meeting the Product specifications. - i…
Note
object
Extra information about a given entity. Only useful in processes involving human interaction. Not applicable for an automated process.
5 properties 5 required
Reason
object
An object to convey a reason for the operation.
1 property 1 required
RelatedContactInformation
object
Contact data for a person or organization that is involved in the product offering qualification. In a given context it is always specified by the Seller (e.g.…
7 properties 4 required
RelatedEntity
object
A reference to an entity, where the type of the entity is not known in advance.
4 properties 3 required
SubUnit
object
Allows for sub unit identification
2 properties 2 required
TroubleTicket
TroubleTicketPriorityType
string
Possible values for the priority of the Trouble Ticket
TroubleTicketSeverityType
string
Possible values for the severity of the Trouble Ticket
TroubleTicketStatusChange
object
Holds the status notification reasons and associated date the status changed, populated by the server
3 properties
TroubleTicketStatusType
string
Possible values for the status of the Trouble Ticket | status | MEF 113 name | Description | | ----------------------- | ---------------------- | -------------…
TroubleTicketType
string
Possible values for the type of the Trouble Ticket: - assistance: Requesting help for a situation (not a failure) requiring attention that is not categorized.…
TroubleTicket_Common
object
A Trouble Ticket is a record of an issue that is created, tracked, and managed by a Trouble Ticket management system Skipped properties: id,href
12 properties 7 required
TroubleTicket_Create
A Trouble Ticket is a record of an issue that is created, tracked, and managed by a Trouble Ticket management system The modeling pattern introduces the Common…
TroubleTicket_Find
object
This class represents a single list item for the response of listTroubleTicket operation.
14 properties 14 required
TroubleTicket_Update
object
A Trouble Ticket is a record of an issue that is created, tracked, and managed by a Trouble Ticket management system
9 properties
WorkOrderRef
object
A reference to an WorkOrder resource.
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mef-lso-cantata-trouble-ticket-management-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-management-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-management-openapi&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mef-lso-cantata-trouble-ticket-management-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 Management (Mef Lso Cantata Trouble Ticket Management), 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.