How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Fenergo Rules API

The Rules API from Fenergo — 5 operation(s) for rules.

Fenergo Rules API is one of 281 APIs that Fenergo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Rules. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 5 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.fenergox.com/tm/observability, https://api.fenergox.com/tm/realtime.

5 operations 5 paths 27 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.fenergox.com/advanceddashboardcommand
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Fenergo Rules API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2_Client_Credentials) using the clientCredentials flow.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 3 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Rules 5
GET
/api/v1/rules/execution
Rules Execution Summary
rules_execution_api_v1_rules_execution_get 4 params → 200400422
POST
/api/rules/execute
Trigger Rule Execution
trigger_rule_execution_api_rules_execute_post body → 200202207403500422
GET
/api/rules/status/{execution_id}
Get Rule Execution Status
get_rule_execution_status_api_rules_status_execution_id_get 1 param → 200400403404422502504
POST
/api/rules/rerun
Rerun Rules
rerun_rules_api_rules_rerun_post body → 200202207400403422429500
GET
/api/rules/schedule
Get Rule Schedule
get_rule_schedule_api_rules_schedule_get 2 params → 200400403404500422

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are RuleExecutionSummary (11 properties), RuleExecutionByExecutionIDSummary (11 properties), RuleExecutionDetail (8 properties), RuleScheduleByRuleIdResponse (6 properties). Each schema is shown below with its type and property counts.

ValidationError
object
5 properties 3 required
RuleExecutionProgress
object
Rule status breakdown for an execution.
4 properties 4 required
RuleExecutionOverallStatus
string
Execution-level status derived from the aggregate of per-rule statuses. Terminal states (iscomplete=True): SUCCEEDED – every rule finished successfully. FAILED…
RuleExecutionByExecutionIDSummary
object
Execution-level summary returned when filtering by executionid.
11 properties 10 required
RuleExecutionStatus
string
RuleExecutionDetail
object
Model for detailed rule execution information.
8 properties 5 required
RuleExecutionRuleDetail
object
Per-rule outcome within an execution-level summary. Omits executionid and ruleeffectivedate — those are at the parent summary level.
6 properties 2 required
HTTPValidationError
object
1 property
RuleExecutionAlerts
object
Aggregated alert counts for an execution. Fields are nullable when the execution is still in progress and no alert data has been indexed yet. They are 0 when t…
2 properties
RuleExecutionsByDateResponse
object
Model for rule executions grouped by run date.
3 properties 3 required
RuleExecutionTiming
object
Timing metrics for an execution.
3 properties 3 required
ExecuteRulesResponseContent
object
4 properties
ValidationError_2
object
3 properties 3 required
ErrorResponse
object
1 property 1 required
RuleExecutionOverallStatus_2
string
Execution-level status derived from the aggregate of per-rule statuses. Terminal states (iscomplete=true): succeeded — every rule finished successfully. failed…
ExecuteRuleGroupsJsonResponse
object
2 properties 2 required
ExecuteRuleGroupsResponseContent
object
4 properties 2 required
RuleExecutionSummary
object
Execution-level summary returned when filtering by executionid.
11 properties 10 required
RejectedRulesResponse
object
2 properties 2 required
ExecuteRulesRequestPayload
object
Request payload for the rule execution endpoint. Attributes: executiondate: The date for which rules should be executed (YYYY-MM-DD). ruleids: Optional list of…
4 properties 1 required
ExecuteRulesJsonResponse
object
2 properties 2 required
ValidationError_3
object
3 properties 3 required
RerunRulesRequestPayload
object
2 properties 2 required
ValidationError_4
object
3 properties 3 required
RuleScheduleItem
object
5 properties 4 required
RuleScheduleByRuleIdResponse
object
6 properties 5 required
RuleScheduleByDateResponse
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-rules-api-openapi.yml Raw ↑

Other APIs Fenergo publishes across the network.

Fenergo Acceptable Document API
Fenergo Access Layer API
Fenergo Adapter Mock API
Fenergo Advanced Dashboard API
Fenergo Agency API
Fenergo Agent API
Fenergo Agent Slos API
Fenergo Agent Value Story API
Fenergo Aggregation API
Fenergo Allocation API
Fenergo Allocation Configuration API
Fenergo Asset API
Where this information came from

This is an independent, third-party profile of Fenergo Rules API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.