The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are FieldedAddressRepresentation (20 properties), TroubleTicket_Find (14 properties), TroubleTicket_Common (12 properties), TroubleTicket_Update (9 properties). Each schema is shown below with its type and property counts.
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.…
SubUnit
object
Allows for sub unit identification
2 properties2 required
AttachmentValue
object
Complements the description of an element (for instance a product) through video, pictures...
8 properties5 required
Error401Code
string
One of the following error codes: - missingCredentials: No credentials provided. - invalidCredentials: Provided credentials are invalid or expired
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…
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 properties4 required
TroubleTicketStatusType
string
Possible values for the status of the Trouble Ticket | status | MEF 113 name | Description | | ----------------------- | ---------------------- | -------------…
TroubleTicketSeverityType
string
Possible values for the severity of the Trouble Ticket
TroubleTicketPriorityType
string
Possible values for the priority of the Trouble Ticket
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…
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 properties1 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…
Unprocessable entity due to a business validation problem. (https://tools.ietf.org/html/rfc4918section-11.2)
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
WorkOrderRef
object
A reference to an WorkOrder resource.
2 properties1 required
Error400
Bad Request. (https://tools.ietf.org/html/rfc7231section-6.5.1)
MEFBuyerSellerType
string
An enumeration with buyer and seller values.
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…
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…
Error404
Resource for the requested path not found. (https://tools.ietf.org/html/rfc7231section-6.5.4)
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
Specification
The full machine-readable OpenAPI contract behind this narrative.
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.
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 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.
