generated: '2026-07-21' method: derived source: >- Derived from this repo's openapi/solaredge-monitoring-openapi.yml, authentication/solaredge-authentication.yml, conventions/solaredge-conventions.yml, errors/solaredge-problem-types.yml and a live probe of monitoringapi.solaredge.com. description: >- Which cross-cutting standards the SolarEdge Monitoring API conforms to. The standout verified finding is that error responses use RFC 9457 problem+json (confirmed live). The API authenticates with an api_key query parameter (not OAuth2/OIDC), is read-only, and returns JSON. standards: - id: rfc9457-problem-details conforms: true evidence: >- Live 401 from monitoringapi.solaredge.com returns application/problem+json with type/title/status/detail/instance/properties.traceId members. - id: oauth2 conforms: false evidence: Authentication is a single api_key query parameter; no oauth2 flows. - id: oidc conforms: false evidence: No /.well-known/openid-configuration (host returns 401 for all paths). - id: apikey-auth conforms: true evidence: securityScheme type apiKey, in query, name api_key. - id: pagination conforms: true evidence: index/size pagination on /sites/list and /accounts/list. - id: idempotency conforms: false evidence: Read-only GET API; no state-changing operations or idempotency-key contract. - id: rfc8594-sunset-header conforms: false evidence: Versioning is exposed via /version/current and /version/supported; no Sunset header documented. - id: webhooks conforms: false evidence: No webhook/event surface; the API is poll-only. - id: fapi conforms: false - id: mtls conforms: false - id: scim conforms: false - id: fhir conforms: false - id: odata conforms: false - id: json-api conforms: false compliance_program: published: false note: >- No public API-scoped security-compliance program (SOC 2 / ISO 27001 certifications) was located for the monitoring platform during this pass; no Compliance pointer emitted.