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 Reference Data API

The Reference Data API from Fenergo — 10 operation(s) for reference data.

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

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

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

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

10 operations 10 paths 22 schemas 10 GET

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 Reference Data 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 10

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

Reference Data 10
GET
/api/reference-data
Get reference data
GetReferenceData 1 param → 200400401403500410
GET
/api/reference-data/users
Get users names
GetUsersNames 1 param → 200400401403500410
GET
/api/reference-data/teams
Get teams names
GetTeamsNames 1 param → 200400401403500410
GET
/api/reference-data/team/{id}
Get team with users by id
GetTeamWithUsersById 2 params → 200400404401403500410
GET
/api/reference-data/access-layers
Get access layers light
GetAccessLayersLight 1 param → 200400401403500410
GET
/api/v2/reference-data
Get reference data
getApiV2ReferenceData 1 param → 200400401403500410
GET
/api/v2/reference-data/users
Get users names
getApiV2ReferenceDataUsers 1 param → 200400401403500410
GET
/api/v2/reference-data/teams
Get teams names
getApiV2ReferenceDataTeams 1 param → 200400401403500410
GET
/api/v2/reference-data/team/{id}
Get team with users by id
getApiV2ReferenceDataTeamById 2 params → 200400404401403500410
GET
/api/v2/reference-data/access-layers
Get access layers light
getApiV2ReferenceDataAccessLayers 1 param → 200400401403500410

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are AccessLayerLightReferenceDto (6 properties), AccessLayersConfigurationReferenceDto (5 properties), AccessLayerReferenceDto (5 properties), ValidationErrorModel (4 properties). Each schema is shown below with its type and property counts.

ServiceResponseMessage
object
The message associated to the service response
3 properties
ReferenceDataDto
object
Response DTO representing reference data
4 properties
TeamWithUsersDtoServiceResponse
object
Service response data
2 properties
StringServiceResponse
object
Service response data
2 properties
TeamReferenceDto
object
Response DTO representing team reference data
3 properties
TeamWithUsersDto
object
Response DTO representing team data
3 properties
ObjectServiceResponse
object
Service response data
2 properties
AccessLayerDataTypeDto
string
TeamNameDtoIEnumerableServiceResponse
object
Service response data
2 properties
AccessLayerTypeDto
string
UserNameDto
object
Response DTO representing user data
2 properties
SensitiveDataKindDto
string
Set of possible values for Sensitive Data parameter
AccessLayerLightReferenceDtoIEnumerableServiceResponse
object
Service response data
2 properties
AccessLayerLightReferenceDto
object
Response DTO representing access layer data
6 properties
TeamNameDto
object
Response DTO representing team data
2 properties
ReferenceDataDtoServiceResponse
object
Service response data
2 properties
ValidationErrorModel
object
Represents the details of validation error
4 properties
AccessLayersConfigurationReferenceDto
object
5 properties
AccessLayerReferenceDto
object
Response DTO representing access layer reference data
5 properties
ValidationErrorModelListServiceResponse
object
Service response data
2 properties
UserNameDtoIEnumerableServiceResponse
object
Service response data
2 properties
UserReferenceDto
object
Response DTO representing user reference data
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-reference-data-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 Reference Data 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.