Discover resources and send IEEE 2030.5 XML over HTTPS REST.
Real servers generally require mutual TLS. Configure your client certificate in the browser / OS, or export a cURL command with certificate paths. Cross-origin servers must allow CORS.
Request settings
Imported XML stays in this page. Choose GET to browse a response example, or PUT / POST to use it as a request body. Validation checks syntax and namespace.
Start the local service, then send GET /dcap.
Request / response
Request preview appears here.
No requests sent
Response content appears here.
Discovered resources
Click a resource to prepare a GET request.
Recent requests (up to 50)
HTTPS and mutual TLS
SEP_TLS_CERT=/path/server.pem SEP_TLS_KEY=/path/server.key npm run qa:ieee2030-server # Add a CA to require client certificates SEP_TLS_CERT=/path/server.pem SEP_TLS_KEY=/path/server.key SEP_TLS_CA=/path/ca.pem npm run qa:ieee2030-server
Trust the server CA and install a client certificate in your browser. For cURL, replace ca.pem, client.pem and client.key with your own files. TLS compatibility depends on your runtime and the target server.
The test service provides DeviceCapability, Time, EndDevice, Registration, assignments, DER programs, controls and DERStatus updates. Its data resets on restart. HTTP mode is for local REST testing. HTTPS mode exercises TLS and optional client authentication.
The 75 original XML examples are from Model Build 20180301. Paths inferred for request-body examples must be checked against your server. Original XML is preserved. Example 16_13_15_MirrorMeterReadingList.xml lacks required list attributes in the supplied XSD.
sep.xsd · Browser validation checks XML syntax and namespace. Use the supplied XSD for schema validation. EXI and automatic subscription callbacks require additional tooling.