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 Tracking Record API

The trackingRecord API from MEF — 1 operation(s) for trackingrecord.

Documentation Provider Profile APIs.io OpenAPI GitHub

MEF Tracking Record API is one of 54 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, API documentation, and an API reference.

This API exposes 1 operation across 1 path, and defines 42 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 6 base URLs: https://{serverBase}/mefApi/allegro/faultManagement/v3/, https://{serverBase}/mefApi/allegro/performanceMonitoring/v5/, https://{serverBase}/mefApi/interlude/faultManagement/v3/, https://{serverBase}/mefApi/interlude/performanceMonitoring/v5/, https://{serverBase}/mefApi/legato/faultManagement/v3/, https://{serverBase}/mefApi/legato/performanceMonitoring/v5/.

1 operations 1 paths 42 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

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

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

trackingRecord 1
GET
/trackingRecord
List or find Tracking Record objects.
listTrackingRecord 6 params → 200400401403422500501

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are PmTrackingRecord (6 properties), PmTrackingRecord_3 (6 properties), FmTrackingRecord (6 properties), PmTrackingRecord_2 (6 properties). Each schema is shown below with its type and property counts.

Error422
Unprocessable entity due to a business validation problem. (https://tools.ietf.org/html/rfc4918section-11.2)
Error400Code
string
One of the following error codes: - missingQueryParameter: The URI is missing a required query-string parameter. - missingQueryValue: The URI is missing a requ…
Error422Code
string
One of the following error codes: - missingProperty: The property that was expected is not present in the payload. - invalidValue: The property has an incorrec…
RelatedObjectRef
object
Reference to the Fault Management Job or Report for which the Tracking Record was created.
FaultManagementJobRef
object
A reference to a Fault Management Job resource.
3 properties 2 required
Error403
Forbidden. This code indicates that the server understood the request but refused to authorize it. (https://tools.ietf.org/html/rfc7231section-6.5.3)
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.
Error400
'Bad Request. (https://tools.ietf.org/html/rfc7231section-6.5.1)'
Error501
Not Implemented. Used in case Seller is not supporting an optional operation. (https://tools.ietf.org/html/rfc7231section-6.6.2)
FaultManagementReportRef
object
A reference to a Fault Management Report resource.
3 properties 2 required
Error500
Internal Server Error. (https://tools.ietf.org/html/rfc7231section-6.6.1)
FmTrackingRecord
object
Tracking Records allow the tracking of modifications of Fault Management Job or Report.
6 properties 3 required
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…
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
Error400Code_2
string
One of the following error codes: - missingQueryParameter: The URI is missing a required query-string parameter - missingQueryValue: The URI is missing a requi…
Error422Code_2
string
One of the following error codes: - missingProperty: The property that was expected is not present in the payload - invalidValue: The property has an incorrect…
RelatedObjectRef_2
object
Reference to the Performance Job, Profile, or Report for which the Tracking Record was created.
Error403_2
Forbidden. This code indicates that the server understood the request but refused to authorize it. (https://tools.ietf.org/html/rfc7231section-6.5.3)
PmTrackingRecord
object
Tracking Records allow the tracking of modifications of Performance Job, Profile, or Report.
6 properties 3 required
Error401_2
'Unauthorized. (https://tools.ietf.org/html/rfc7235section-3.1)'
Error401Code_2
string
One of the following error codes: - missingCredentials: No credentials provided - invalidCredentials: Provided credentials are invalid or expired.
PerformanceProfileRef
object
A reference to a Performance Profile resource.
3 properties 2 required
Error400_2
'Bad Request. (https://tools.ietf.org/html/rfc7231section-6.5.1)'
PerformanceJobRef
object
A reference to a Performance Job resource.
3 properties 2 required
PerformanceReportRef
object
A reference to a Performance Report resource.
3 properties 2 required
Error400Code_3
string
One of the following error codes: - missingQueryParameter: The URI is missing a required query-string parameter - missingQueryValue: The URI is missing a requi…
Error422Code_3
string
One of the following error codes: - missingProperty: The property that was expected is not present in the payload - invalidValue: The property has an incorrect…
RelatedObjectRef_3
object
Reference to the Performance Job, Profile, or Report for which the Tracking Record was created.
Error403_3
Forbidden. This code indicates that the server understood the request but refused to authorize it. (https://tools.ietf.org/html/rfc7231section-6.5.3)
PmTrackingRecord_2
object
Tracking Records allow the tracking of modifications of Performance Job, Profile, or Report.
6 properties 3 required
Error401_3
'Unauthorized. (https://tools.ietf.org/html/rfc7235section-3.1)'
Error401Code_3
string
One of the following error codes: - missingCredentials: No credentials provided - invalidCredentials: Provided credentials are invalid or expired.
Error400_3
'Bad Request. (https://tools.ietf.org/html/rfc7231section-6.5.1)'
Error400Code_4
string
One of the following error codes: - missingQueryParameter: The URI is missing a required query-string parameter - missingQueryValue: The URI is missing a requi…
Error422Code_4
string
One of the following error codes: - missingProperty: The property that was expected is not present in the payload - invalidValue: The property has an incorrect…
RelatedObjectRef_4
object
Reference to the Performance Job, Profile, or Report for which the Tracking Record was created.
Error403_4
Forbidden. This code indicates that the server understood the request but refused to authorize it. (https://tools.ietf.org/html/rfc7231section-6.5.3)
PmTrackingRecord_3
object
Tracking Records allow the tracking of modifications of Performance Job, Profile, or Report.
6 properties 3 required
Error401_4
'Unauthorized. (https://tools.ietf.org/html/rfc7235section-3.1)'
Error401Code_4
string
One of the following error codes: - missingCredentials: No credentials provided - invalidCredentials: Provided credentials are invalid or expired.
Error400_4
'Bad Request. (https://tools.ietf.org/html/rfc7231section-6.5.1)'

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mef-trackingrecord-api-openapi.yml Raw ↑

Other APIs MEF publishes across the network.

MEF LSO Interlude MEF 133.1 streaming template
AE Profile APIs.io
MEF Alarm API
AE Profile APIs.io
MEF Appointment API
AE Profile APIs.io
MEF appointment operations API
AE Profile APIs.io
MEF Cancel Product Order API
AE Profile APIs.io
MEF Cancel Test Job API
AE Profile APIs.io
MEF Category API
AE Profile APIs.io
MEF Charge API
AE Profile APIs.io
MEF CIM Incident API
AE Profile APIs.io
MEF Customer Bill API
AE Profile APIs.io
MEF Event listeners API
AE Profile APIs.io
MEF events subscription API
AE Profile APIs.io
← Back to M APIs
API Details
ID
mef:mef-trackingrecord-api
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-trackingrecord-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mef-trackingrecord-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 MEF Tracking Record 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.