Xoserve · OpenAPI Overlay 1.0.0
API Evangelist enhancements for Xoserve Meter Asset v1
4 actions
4 updates
update
extends
openapi/xoserve-meter-asset-api-v1-openapi.yml
Derived by API Evangelist
Built from the contracts Xoserve publishes. Xoserve did not publish this file.
What the actions change
/MeterAssetRestResponseMeterAssetx-apievangelist-rating-sourcex-access-gate
Targets 4
$.servers
$.paths
$.components.schemas
$.info
OpenAPI Overlay
overlay: 1.0.0
info:
title: API Evangelist enhancements for Xoserve Meter Asset v1
version: 1.0.0
extends: openapi/xoserve-meter-asset-api-v1-openapi.yml
x-apievangelist:
generated: '2026-07-27'
method: searched
source: https://discoveryapiportal.correla.com/developer/apis/meter-asset/operations/getMeterAsset_1?api-version=2022-04-01-preview
(operation detail, HTTP 200) and https://discoveryapiportal.correla.com/developer/apis/meter-asset/schemas/62d80a029d9dc200d05e80f6?api-version=2022-04-01-preview
(components schema document, HTTP 200); 401/404 response shapes captured from live probes of https://discoveryapi.correla.com/
on 2026-07-27
rationale: 'Azure API Management strips paths and components from the anonymous OpenAPI export, so the harvested
openapi/ file carries `paths: {}`. Every element added by this overlay was retrieved verbatim from Xoserve/Correla''s
own developer-portal API — nothing is invented. Applying the overlay reconstitutes the operation the provider
publishes.'
actions:
- target: $.servers
update:
- url: https://discoveryapi.correla.com/meter-asset/v1
description: Live gateway, segment-versioned (v1). Confirmed 401 (subscription key required) on 2026-07-27.
- target: $.paths
update:
/:
get:
operationId: getMeterAsset_1
summary: Meter Asset
description: Meter Asset
tags:
- Meter Asset
parameters:
- name: mprn
in: query
required: false
description: Format - int64. Meter Point Reference Number (MRPN). A unique identifier for the point at
which a meter is, has been or will be connected to the Gas Network
schema:
type: integer
- name: msn
in: query
required: false
description: The manufacturer's meter serial number as held on the physical meter currently installed
on the supply point
schema:
type: string
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/MeterAssetRestResponse'
example:
meter:
mprn: string
msn: string
current_supplier: string
current_supplier_name: string
meter_capacity: string
meter_mechanism: string
meter_type: string
meter_model: string
meter_year_of_manufacture: string
smp_status: string
meter_installation_date: string
meter_asset_manager_effective_date: string
meter_asset_manager_id: string
meter_asset_manager_name: string
service_effective_valid_from: string
map_id: string
application/xml:
schema:
$ref: '#/components/schemas/MeterAsset'
example: <meter> <mprn>string</mprn> <msn>string</msn> <current_supplier>string</current_supplier>
<current_supplier_name>string</current_supplier_name> <meter_capacity>string</meter_capacity>
<meter_mechanism>string</meter_mechanism> <meter_type>string</meter_type> <meter_model>string</meter_model>
<meter_year_of_manufacture>string</meter_year_of_manufacture> <meter_installation_date>string</meter_installation_date>
<meter_asset_manager_effective_date>string</meter_asset_manager_effective_date> <meter_asset_manager_id>string</meter_asset_manager_id>
<meter_asset_manager_name>string</meter_asset_manager_name> <service_effective_valid_from>string</service_effective_valid_from>
<map_id>string</map_id> </meter>
'401':
description: Access denied — missing or invalid Azure API Management subscription key.
content:
application/json:
example:
statusCode: 401
message: Access denied due to missing subscription key. Make sure to include subscription key
when making requests to an API.
'404':
description: Resource not found.
content:
application/json:
example:
statusCode: 404
message: Resource not found
- target: $.components.schemas
update:
MeterAssetRestResponse:
type: object
properties:
meter:
$ref: '#/components/schemas/MeterAsset'
xml:
name: root
example:
meter:
mprn: string
msn: string
current_supplier: string
current_supplier_name: string
meter_capacity: string
meter_mechanism: string
meter_type: string
meter_model: string
meter_year_of_manufacture: string
smp_status: string
meter_installation_date: string
meter_asset_manager_effective_date: string
meter_asset_manager_id: string
meter_asset_manager_name: string
service_effective_valid_from: string
map_id: string
MeterAsset:
type: object
properties:
mprn:
type: string
description: Meter Point Reference Number (MRPN). A unique identifier for the point at which a meter is,
has been or will be connected to the Gas Network
msn:
type: string
description: The manufacturer's meter serial number as held on the physical meter currently installed
on the supply point
current_supplier:
type: string
description: A unique three character code used to identify the current supplier
current_supplier_name:
type: string
description: Name of the current Supplier
meter_capacity:
type: string
description: The amount of gas that can be passed through the meter in a given time period. This is the
manufacturer's maximum value
meter_mechanism:
type: string
description: The coded value of the description of the Meter Mechanism
meter_type:
type: string
description: The type of meter installed at the supply point
meter_model:
type: string
description: Model of meter installed at the supply point
meter_year_of_manufacture:
type: string
description: The year of manufacture of the meter installed at the supply point
smp_status:
type: string
description: (Upcoming version) The current status of the operability of the supply meter point
meter_installation_date:
type: string
description: The date of when the meter was installed
format: date-time
meter_asset_manager_effective_date:
type: string
description: The date of when the MAM became effective for the Supply Point
format: date-time
meter_asset_manager_id:
type: string
description: An identification number for the registered MAM for the Supply Point
meter_asset_manager_name:
type: string
description: The company name of the registered MAM for the Supply Point
service_effective_valid_from:
type: string
description: The date of when the service becomes effective for the Supply Point
format: date-time
map_id:
type: string
description: MAP ID
description: A Meter Asset object
xml:
name: meter
example:
mprn: string
msn: string
current_supplier: string
current_supplier_name: string
meter_capacity: string
meter_mechanism: string
meter_type: string
meter_model: string
meter_year_of_manufacture: string
smp_status: string
meter_installation_date: string
meter_asset_manager_effective_date: string
meter_asset_manager_id: string
meter_asset_manager_name: string
service_effective_valid_from: string
map_id: string
- target: $.info
update:
x-apievangelist-rating-source: https://apis.io/provider/xoserve
x-access-gate: accredited-only — subscription AND approval required; keys issued after contract countersigning
Work with this as data
Every overlay here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for openapi overlays
4 MCP tools reach this
find_overlaysBrowse and filter every overlay in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/xoserve-meter-asset-api-v1-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.