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 Nebula Authorization Command 1.0

Fenergo Nebula Authorization Command — OpenAPI 3.0.4 contract published by Fenergo for the authorizationcommand service of the Fen-X SaaS platform, carrying 14 path(s) and 19 operation(s). Harvested verbatim from Fenergo's own published specification endpoint.

Fenergo Nebula Authorization Command 1.0 is one of 145 APIs that Fenergo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authorization, Command, Compliance, and Financial Services. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 19 operations across 14 paths, organized into 4 resource areas, and defines 52 schemas. It is described by OpenAPI 3.0.4, at version 1.0.

Requests are made against a single base URL, /authorizationcommand.

19 operations 14 paths 52 schemas 5 DELETE5 POST9 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.4
API Version
1.0
Base URL
https://api.fenergox.com/authorizationcommand
Authentication
API Key
Resource Areas
4

Authentication & Security 1

Fenergo Nebula Authorization Command 1.0 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 19

Across 14 paths, the API surfaces 19 operations — 5 DELETE, 5 POST, 9 PUT. They span 4 resource areas: AccessLayer, DynamicConfiguration, RelatedPartyAccessLayersInheritanceConfiguration, Team. Each is listed below with its method, path, parameters, and response codes.

AccessLayer 7
POST
/api/access-layer
Create access layer
CreateAccessLayer 1 param body → 202400401403500410
PUT
/api/access-layer/{id}
Update access layer
UpdateAccessLayer 2 params body → 202400404409401403500410
DELETE
/api/access-layer/{id}
Delete access layer
DeleteAccessLayer 2 params → 202400404409401403500410
PUT
/api/access-layer/{id}/user/{userId}
Assign user to the access layer
AssignUserToAccessLayer 3 params → 202400404409401403500410
DELETE
/api/access-layer/{id}/user/{userId}
Unassign user from the access layer
UnassignUserFromAccessLayer 3 params → 202400404409401403500410
PUT
/api/access-layer/users/{userId}/batch
Batch update user access layers
BatchUpdateUserAccessLayers 2 params body → 202400404401403500410
PUT
/api/access-layer/configuration
Update access layers-related configuration
UpdateAccessLayersConfiguration 1 param body → 202409400401403500410
DynamicConfiguration 4
POST
/api/dynamic-configuration
Create dynamic configuration
CreateDynamicConfiguration 1 param body → 202400401403500410
POST
/api/dynamic-configuration/{id}/clone
Clone dynamic configuration
CloneDynamicConfiguration 2 params body → 202400401403500410
PUT
/api/dynamic-configuration/{id}
Update dynamic configuration
UpdateDynamicConfiguration 2 params body → 202400404409401403500410
DELETE
/api/dynamic-configuration/{id}
Delete dynamic configuration
DeleteDynamicConfiguration 2 params → 202400404409401403500410
RelatedPartyAccessLayersInheritanceConfiguration 1
PUT
/api/related-party-access-layers-inheritance-configuration/update
Update access layers inheritance configuration
UpdateRelatedPartyAccessLayersInheritanceConfiguration 1 param body → 202409400401403500410
Team 7
POST
/api/team
Create team
CreateTeam 1 param body → 202400401403500410
PUT
/api/team/{id}
Update team
UpdateTeam 2 params body → 202409400404401403500410
DELETE
/api/team/{id}
Delete team
DeleteTeam 2 params → 202400404409401403500410
POST
/api/team/{id}/clone
Clone team
CloneTeam 2 params body → 202400404401403500410
PUT
/api/team/{id}/user/{userId}
Add User to the team
AddUserToTeam 3 params → 202400404409401403500410
DELETE
/api/team/{id}/user/{userId}
Remove user from the team
RemoveUserFromTeam 3 params → 202400404409401403500410
PUT
/api/team/users/{userId}/batch
Batch update user teams
BatchUpdateUsers 2 params body → 202400404401403500410

Schemas 52

The contract defines 52 schemas that model the data the API accepts and returns. The most detailed are ConditionDefinitionDto (9 properties), UpdateDynamicConfigurationRequestDto (7 properties), CreateAccessLayerRequestDto (7 properties), UpdateAccessLayerRequestDto (6 properties). Each schema is shown below with its type and property counts.

AccessLayerDataTypeDto
string
AccessLayerTypeDto
string
BatchUpdateUserAccessLayersRequestDto
object
Batch update users request data
1 property
BatchUpdateUserAccessLayersRequestDtoServiceRequest
object
Service request data
1 property
BatchUpdateUsersRequestsDto
object
Batch update users request data
1 property
BatchUpdateUsersRequestsDtoServiceRequest
object
Service request data
1 property
CloneDynamicConfigurationRequestDto
object
Request DTO representing dynamic configuration data to clone
1 property
CloneDynamicConfigurationRequestDtoServiceRequest
object
Service request data
1 property
CloneDynamicConfigurationResponseDto
object
Response DTO representing cloned dynamic configuration data
1 property
CloneDynamicConfigurationResponseDtoServiceResponse
object
Service response data
2 properties
CloneTeamRequestDto
object
Request DTO representing team data to clone
1 property
CloneTeamRequestDtoServiceRequest
object
Service request data
1 property
CloneTeamResponseDto
object
Response DTO representing cloned team data
1 property
CloneTeamResponseDtoServiceResponse
object
Service response data
2 properties
ConditionDefinitionDto
object
Represents condition
9 properties
ConditionDto
object
Represents condition root
5 properties 2 required
CreateAccessLayerRequestDto
object
Request DTO representing access layer data to create
7 properties
CreateAccessLayerRequestDtoServiceRequest
object
Service request data
1 property
CreateAccessLayerResponseDto
object
Response DTO representing created access layer
1 property
CreateAccessLayerResponseDtoServiceResponse
object
Service response data
2 properties
CreateDynamicConfigurationRequestDto
object
Request DTO representing dynamic configuration to create
6 properties
CreateDynamicConfigurationRequestDtoServiceRequest
object
Service request data
1 property
CreateDynamicConfigurationResponseDto
object
Response DTO representing created dynamic configuration
1 property
CreateDynamicConfigurationResponseDtoServiceResponse
object
Service response data
2 properties
CreateTeamRequestDto
object
Request DTO representing team data to create
4 properties
CreateTeamRequestDtoServiceRequest
object
Service request data
1 property
CreateTeamResponseDto
object
Response DTO representing created team
1 property
CreateTeamResponseDtoServiceResponse
object
Service response data
2 properties
ObjectServiceResponse
object
Service response data
2 properties
SensitiveDataKindDto
string
Set of possible values for Sensitive Data parameter
ServiceResponse
object
Service response data
2 properties
ServiceResponseMessage
object
The message associated to the service response
3 properties
StringServiceResponse
object
Service response data
2 properties
UpdateAccessLayerRequestDto
object
Request DTO representing access layer data to update
6 properties
UpdateAccessLayerRequestDtoServiceRequest
object
Service request data
1 property
UpdateAccessLayerResponseDto
object
Response DTO representing updated access layer
1 property
UpdateAccessLayerResponseDtoServiceResponse
object
Service response data
2 properties
UpdateAccessLayersConfigurationRequestDto
object
6 properties 5 required
UpdateAccessLayersConfigurationRequestDtoServiceRequest
object
Service request data
1 property
UpdateDynamicConfigurationRequestDto
object
Request DTO representing dynamic configuration data to update
7 properties
UpdateDynamicConfigurationRequestDtoServiceRequest
object
Service request data
1 property
UpdateDynamicConfigurationResponseDto
object
Response DTO representing updated dynamic configuration
1 property
UpdateDynamicConfigurationResponseDtoServiceResponse
object
Service response data
2 properties
UpdateInheritanceConfigurationRequestDto
object
Request DTO representing related party access layers inheritance configuration data to update
1 property
UpdateInheritanceConfigurationRequestDtoServiceRequest
object
Service request data
1 property
UpdateTeamRequestDto
object
Request DTO representing team data to update
5 properties
UpdateTeamRequestDtoServiceRequest
object
Service request data
1 property
UpdateTeamResponseDto
object
Response DTO representing updated team
1 property
UpdateTeamResponseDtoServiceResponse
object
Service response data
2 properties
ValidationErrorModel
object
Represents the details of validation error
4 properties
ValidationErrorModelListServiceResponse
object
Service response data
2 properties
ValueField
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-authorizationcommand-v1-0-openapi.json Raw ↑

Other APIs Fenergo publishes across the network.

Fenergo Nebula Advanced Dashboard Command 1.0
Fenergo Nebula Advanced Dashboard Query 1.0.0
Fenergo Nebula Association Command 1.0
Fenergo Nebula Association Command 2.0
Fenergo Nebula Association Query 1.0
Fenergo Nebula Audit Query 1.0
Fenergo Nebula Audit Query 2.0
Fenergo Nebula Audit Query 3.0
Fenergo Nebula Authorization Query 1.0
Fenergo Nebula Authorization Query 2.0
Fenergo Nebula Authorization Query 3.0
Fenergo Nebula BulkLoad Command 1.0
Where this information came from

This is an independent, third-party profile of Fenergo Nebula Authorization Command 1.0, 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.