Supply Point Enquiry API Technical Specification Updates
Summary
The content detailed in Section 4.2 Responses is incorrect. We would like to amend the responses included in this section so that users are able to access the correct technical specifications for the service that they are consuming.
Latest update and next planned activity
Date of latest update
Latest Update
10/02/2025 - Change withdrawn and will be progressed as a Housekeeping change under R0239 Housekeeping Feb 2025. The adoption window has now closed.
Impacts Overview
Priority and rationale
Standard
Solution development
Problem Statement
The example responses detailed in section 4.2 are broken down as ‘mprn’ with three demoed data items; ‘mprn’, ‘installation name’, and ‘network name.’ this is however not reflective of the correct responses that would actually be returned on an API call. The actual structure is ‘supplier’ with the demoted data items actually being ‘amr_indicator’, ‘amr-sp’, and ‘csep_id.’ Fundamentally, this would mean that users are consuming incorrect information when looking to this document for guidance. This could potentially be causing negative impacts when the document is relied upon, especially for newer users seeking guidance.
Change Plan
Change discussed at Change Panel
Completed
Start:
Due:
Completion:
21 Jan 2025Original submission
Change details
Molly Haley - Xoserve
5 Dec 2024
Change details
Supply Point Enquiry API Technical Specification Updates
The content detailed in Section 4.2 Responses is incorrect. We would like to amend the responses included in this section so that users are able to access the correct technical specifications for the service that they are consuming.
Users are consuming incorrect information when using the tech specs, which could be causing downstream impacts to processes. The purpose of section 4.2 is to state that there will be only one record returned for each input, but it displayed a table with four data items listed as being the first four outputs in an API call: ‘mprn’ and then ‘installation name,’ ‘network name’ and ‘mprn’ demoted. However, the first four data items returned on an API call are ‘supplier’ and then the demoted ‘amr_indicator’, ‘amr_sp’ and ‘csep_id.’
Inserting the correct responses into section 4.2. Section 4.2 'Responses' in the supporting document have now been updated to show the correct order of API data outputs i.e. ‘supplier’ and then the demoted ‘amr_indicator’, ‘amr_sp’ and ‘csep_id.’
-
Impacts
Gas
Trust and confidence, Other (please provide details in Additional information box below)
I am unsure on which benefits to tick in the section above
No details provided
-
No details provided
-
No details provided
-
No details provided
-
GES Supply Point Enquiry API Technical Specification
-
No details provided
-
Energy Suppliers, Shippers
Unsure which other REC parties will be impacted
No details provided
-
No
No details provided
Priority & timing
No
Although this Change is not urgent, it is very important that the correct Tech Spec is being shared with new users, so this Change should be progressed quickly and our suggestion would be to share the new version with new users if they sign up in the meantime.
Development: The solution is to replace section 4.2 which we have already done in the supporting document.
Implementation: ASAP
Implementation: ASAP
-
No details provided
Trust and confidence, Other (please provide details in the Additional information box below)