Enphase Energy · API Governance Rules
Enphase Energy API Rules
Spectral linting rules defining API design standards and conventions for Enphase Energy.
6 Rules
error 1
warn 3
info 2
Rule Categories
enphase
Rules
error
enphase-paths-must-be-versioned
All Enphase Enlighten Systems API paths must include /api/v4/ (or /api/v2/ for legacy specs).
$.paths.*~
warn
enphase-operation-summary-title-case
Operation summaries should use Title Case for consistency with API Evangelist catalog conventions.
$.paths.*.*.summary
warn
enphase-oauth2-required
v4 operations should require OAuth 2.0 security plus the application API key.
$.paths[?(@property =~ /^\/api\/v4\//)].*.security
warn
enphase-system-id-parameter
System-scoped paths must declare the system_id path parameter as integer.
$.paths[?(@property.indexOf('{system_id}') > -1)].*.parameters[?(@.name == 'system_id')]
info
enphase-date-params-iso-format
start_date and end_date parameters should be string format=date (YYYY-MM-DD).
$.paths.*.*.parameters[?(@.name == 'start_date' || @.name == 'end_date')]
info
enphase-throttle-409-documented
Operations should document the 409 Conflict response that Enphase returns when per-minute throttle is exceeded.
$.paths.*.get.responses