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 Query 3.0

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

Fenergo Nebula Authorization Query 3.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, Query, Compliance, and Financial Services. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 7 paths, organized into 2 resource areas, and defines 23 schemas. It is described by OpenAPI 3.0.4, at version 3.0.

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

7 operations 7 paths 23 schemas 7 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.4
API Version
3.0
Base URL
https://api.fenergox.com/authorizationquery
Authentication
API Key
Resource Areas
2

Authentication & Security 1

Fenergo Nebula Authorization Query 3.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 7

Across 7 paths, the API surfaces 7 operations — 7 GET. They span 2 resource areas: AccessLayer, Team. Each is listed below with its method, path, parameters, and response codes.

AccessLayer 4
GET
/api/v3/access-layer/{id}
Get access layer by id
GetAccessLayer 2 params → 200400404401403500410
GET
/api/v3/access-layer/{id}/users
Get users with given access layer assigned
GetAccessLayerUsers 2 params → 200400401403500410
GET
/api/v3/access-layer/configuration
Get access layers configuration
GetAccessLayersConfiguration 1 param → 200400401403500410
GET
/api/v3/access-layer
Get paged access layers
GetAccessLayersPaged 3 params → 200400401403500410
Team 3
GET
/api/v3/team/{id}
Get team by id
GetTeam 2 params → 200400404401403500410
GET
/api/v3/team/{id}/users
Get user teams
GetTeamUsers 2 params → 200400401403500410
GET
/api/v3/team
Get paged teams
GetAllTeamsPaged 4 params → 200400401403500410

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are AccessLayerLightDto (10 properties), AccessLayerDto (10 properties), TeamDto (7 properties), AccessLayersConfigurationDto (6 properties). Each schema is shown below with its type and property counts.

AccessLayerDataTypeDto
string
AccessLayerDto
object
Response DTO representing access layer data
10 properties
AccessLayerDtoServiceResponse
object
Service response data
2 properties
AccessLayerLightDto
object
Response DTO representing access layer data
10 properties
AccessLayerLightDtoItemsPage
object
Query Result Page
2 properties
AccessLayerLightDtoItemsPageServiceResponse
object
Service response data
2 properties
AccessLayerTypeDto
string
AccessLayersConfigurationDto
object
Response DTO representing access layers configuration
6 properties
AccessLayersConfigurationDtoServiceResponse
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
StringIEnumerableServiceResponse
object
Service response data
2 properties
StringServiceResponse
object
Service response data
2 properties
TeamDto
object
Response DTO representing team data
7 properties
TeamDtoServiceResponse
object
Service response data
2 properties
TeamLightDto
object
Response DTO representing team data
4 properties
TeamLightWithUsersCountDto
Response DTO representing team data
TeamLightWithUsersCountDtoItemsPage
object
Query Result Page
2 properties
TeamLightWithUsersCountDtoItemsPageServiceResponse
object
Service response data
2 properties
ValidationErrorModel
object
Represents the details of validation error
4 properties
ValidationErrorModelListServiceResponse
object
Service response data
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-authorizationquery-v3-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 Command 1.0
Fenergo Nebula Authorization Query 1.0
Fenergo Nebula Authorization Query 2.0
Fenergo Nebula BulkLoad Command 1.0
Where this information came from

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