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 Allocation Configuration API

The AllocationConfiguration API from Fenergo — 7 operation(s) for allocationconfiguration.

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

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

This API exposes 11 operations across 7 paths, and defines 38 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: /financialanalysiscommand, /financialanalysisquery.

11 operations 7 paths 38 schemas 1 DELETE3 GET3 POST4 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 Allocation Configuration 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 11

Across 7 paths, the API surfaces 11 operations — 1 DELETE, 3 GET, 3 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

AllocationConfiguration 11
POST
/api/configuration/allocation
Create a new Capacity to Service Configuration
CreateAllocationConfiguration 1 param body → 202400404401403500410
GET
/api/configuration/allocation
Get all Capacity to Service Configurations for the client tenant
GetAllAllocationConfigurations 1 param → 200400401403500410
DELETE
/api/configuration/allocation/{configurationId}
Delete Capacity to Service Configuration and all it's versions
DeleteAllocationConfiguration 2 params → 202400404401403500410
POST
/api/configuration/allocation/{configurationId}
Create a new Version for an existing Capacity to Service Configuration
CreateAllocationConfigurationVersion 2 params body → 202400404401403500410
GET
/api/configuration/allocation/{configurationId}
Get an active version of an existing Capacity to Service Configuration by ID
GetAllocationConfigurationById 2 params → 200400404401403500410
POST
/api/configuration/allocation/{configurationId}/version/{versionNumber}/clone
Clone a Capacity to Service Configuration
CloneAllocationConfiguration 3 params body → 202400404401403500410
PUT
/api/configuration/allocation/{configurationId}/version/{versionNumber}
Updates an existing Version of a Capacity to Service Configuration
UpdateAllocationConfigurationVersion 3 params body → 202400404401403500410
GET
/api/configuration/allocation/{configurationId}/version/{versionNumber}
Get a specific version of an existing Capacity to Service Configuration
GetAllocationConfigurationVersionByVersionNumber 3 params → 200400404401403500410
PUT
/api/configuration/allocation/{configurationId}/version/{versionNumber}/submit-for-approval
Submit an existing Version of a Capacity to Service Configuration for Approval
SubmitAllocationConfigurationVersion 3 params → 202400404401403500410
PUT
/api/configuration/allocation/{configurationId}/version/{versionNumber}/sign
Sign an existing Version of a Capacity to Service Configuration
SignAllocationConfigurationVersion 3 params body → 202400404401403500410
PUT
/api/configuration/allocation/{configurationId}/version/{versionNumber}/archive
Archive an existing Version of a Capacity to Service Configuration
ArchiveAllocationConfigurationVersion 3 params → 202400404401403500410

Schemas 38

The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are AllocationConfigurationVersionDto_2 (23 properties), AllocationConfigurationVersionDto (19 properties), AllocationEntityTypeConfigurationDto_2 (7 properties), AllocationEntityTypeConfigurationDto (7 properties). Each schema is shown below with its type and property counts.

AllocationConfigurationClonedResponseDto
object
Configuration Clone response data
1 property
ServiceResponseMessage
object
3 properties
AllocationConfigurationClonedResponseDtoServiceResponse
object
2 properties
AllocationConfigurationVersionSignedResponseDtoServiceResponse
object
2 properties
StringServiceResponse
object
2 properties
StandardValidationDataDto
object
Request DTO representing validation data metadata
5 properties
Approver
object
4 properties
AllocationEntityTypeConfigurationDto
object
7 properties
ObjectServiceResponse
object
2 properties
ServiceResponse
object
2 properties
AllocationConfigurationVersionDto
object
Set of properties which define new version of Capacity to Service Configuration
19 properties
ConditionOperatorDto
object
Set of properties which define a Scoping Condition Operator
5 properties
AllocationValidationDataDto
object
Request DTO representing business validation data metadata
2 properties
Decision
string
AllocationConfigurationCloneRequestDtoServiceRequest
object
1 property
BasicRuleDto
object
Request DTO representing basic validation rule metadata
2 properties
AllocationConfigurationVersionDtoServiceRequest
object
1 property
Signee
object
4 properties
ValidationErrorModel
object
4 properties
ConditionOperatorItemDto
object
Set of properties which define a Condition Operator Item
6 properties
AllocationConfigurationCloneRequestDto
object
Configuration Clone response data
1 property
ValidationErrorModelListServiceResponse
object
2 properties
AllocationConfigurationVersionDtoServiceResponse
object
2 properties
ApproveAction
object
3 properties
ValueLimitRuleDto
object
Request DTO representing value limit rule metadata
4 properties
VersionStatus
string
AllocationConfigurationVersionSignedResponseDto
object
Contains the new version Status, after a version sign operation
3 properties
ApproveActionServiceRequest
object
1 property
AllocationConfigurationDto
object
Capacity to Service Configuration Data
2 properties
StandardValidationDataDto_2
object
Request DTO representing validation data metadata
5 properties
Approver_2
object
4 properties
AllocationEntityTypeConfigurationDto_2
object
7 properties
AllocationConfigurationVersionDto_2
object
Instance of Capacity to Service Configuration Version
23 properties
AllocationValidationDataDto_2
object
Request DTO representing business validation data metadata
2 properties
AllocationConfigurationDtoIEnumerableServiceResponse
object
2 properties
Signee_2
object
4 properties
AllocationConfigurationVersionDtoServiceResponse_2
object
2 properties
ApproveAction_2
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-allocationconfiguration-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 Asset API
Fenergo Asset Draft API
Where this information came from

This is an independent, third-party profile of Fenergo Allocation Configuration 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.