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 Jurisdiction API

The Jurisdiction API from Fenergo — 8 operation(s) for jurisdiction.

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

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

This API exposes 9 operations across 8 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: /policycommand, /policyquery.

9 operations 8 paths 23 schemas 1 DELETE5 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.fenergox.com/advanceddashboardcommand
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Fenergo Jurisdiction API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer). By default, every request must be authenticated.

  • Bearer — Please insert JWT with Bearer into field

Paths & Operations 9

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

Jurisdiction 9
POST
/api/v2/policies/{entityPolicyId}/jurisdictions
Create a new policy jurisdiction
CreatePolicyJurisdiction 3 params body → 202400404401403500410
PUT
/api/v2/policies/{entityPolicyId}/jurisdictions/{jurisdictionId}
Update a policy jurisdiction
UpdatePolicyJurisdiction 4 params body → 202400404401403500410
DELETE
/api/v2/policies/{entityPolicyId}/jurisdictions/{jurisdictionId}
Delete a policy jurisdiction
DeletePolicyJurisdiction 4 params → 202400404401403500410
PUT
/api/v2/policies/{entityPolicyId}/jurisdictions/{jurisdictionId}/revert
Revert a policy jurisdiction changes
RevertPolicyJurisdiction 4 params → 202400404401403500410
GET
/api/v4/policies/{entityPolicyId}/jurisdictions
Get jurisdictions from the current version of the policy
ListJurisdictions 5 params → 200400401403500410
GET
/api/v4/policies/{entityPolicyId}/version/{versionNumber}/jurisdictions
Get jurisdictions from a specific version of the policy
ListHistoricJurisdictions 5 params → 200400401403500410
GET
/api/v4/policies/{entityPolicyId}/jurisdictions/{jurisdictionId}
Get specific jurisdiction from a specific version of the policy
GetJurisdiction 4 params → 200400404401403500410
GET
/api/v4/policies/{entityPolicyId}/version/{versionNumber}/jurisdictions/{jurisdictionId}
Get specific jurisdiction from a specific version of the policy
GetHistoricJurisdiction 4 params → 200400404401403500410
GET
/api/v4/policies/{entityPolicyId}/jurisdictions/available
Get all current jurisdictions for a given policy
ListAvailableJurisdictions 3 params → 200400401403500410

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are ConditionDefinitionDto (9 properties), JurisdictionViewModelDto (8 properties), JurisdictionListItemViewModelDto (7 properties), ConditionDto_2 (5 properties). Each schema is shown below with its type and property counts.

CreateEntityPolicyJurisdictionRequestDto
object
Create jurisdiction request
3 properties 2 required
CreateEntityPolicyJurisdictionResponseDtoServiceResponse
object
Service response data
2 properties
UpdateEntityPolicyJurisdictionResponseDtoServiceResponse
object
Service response data
2 properties
ServiceResponseMessage
object
The message associated to the service response
3 properties
UpdateEntityPolicyJurisdictionRequestDtoServiceRequest
object
Service request data
1 property
UpdateEntityPolicyJurisdictionRequestDto
object
Create jurisdiction request
3 properties 2 required
CreateEntityPolicyJurisdictionResponseDto
object
Create jurisdiction response
1 property 1 required
CreateEntityPolicyJurisdictionRequestDtoServiceRequest
object
Service request data
1 property
ConditionDto
object
Represents condition root
5 properties 3 required
UpdateEntityPolicyJurisdictionResponseDto
object
Update jurisdiction response
1 property 1 required
ProblemDetails
object
5 properties
ConditionDefinitionDto
object
Represents condition
9 properties
ValueField
object
2 properties
JurisdictionViewModelDtoServiceResponse
object
Service response data
2 properties
JurisdictionNameViewModelDtoItemsPage
object
Query Result Page
2 properties
JurisdictionListItemViewModelDtoItemsPage
object
Query Result Page
2 properties
JurisdictionNameViewModelDtoItemsPageServiceResponse
object
Service response data
2 properties
LockDetailsDto
object
3 properties
JurisdictionListItemViewModelDto
object
Jurisdiction
7 properties
JurisdictionListItemViewModelDtoItemsPageServiceResponse
object
Service response data
2 properties
ConditionDto_2
object
Represents condition root
5 properties
JurisdictionViewModelDto
object
8 properties
JurisdictionNameViewModelDto
object
Jurisdiction DTO
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-jurisdiction-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 Jurisdiction 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.