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

The Clients API from Fenergo — 5 operation(s) for clients.

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

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

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

Requests are made against 2 base URLs: /identitymanagementcommand, /identitymanagementquery.

10 operations 5 paths 24 schemas 2 DELETE5 GET1 PATCH2 POST

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 Clients 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 5 paths, the API surfaces 10 operations — 2 DELETE, 5 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Clients 10
POST
/api/clients
Adds a new client to the tenant, with the data specified in the request
CreateClient 1 param body → 200400409500401403410
GET
/api/clients
Returns all clients from the tenant
GetClients 3 params → 200400500401403410
DELETE
/api/clients/{clientId}
Removes an existing client from the tenant
DeleteClient 2 params → 200400404500401403410
PATCH
/api/clients/{clientId}
Updates some data of a client that already exists in the tenant
PatchClient 2 params body → 200400404500401403410
GET
/api/clients/{clientId}
Returns the client with the specified id
GetClientById 2 params → 200400404500401403410
POST
/api/clients/{clientId}/secrets
Adds a new secret to the client
CreateClientSecret 2 params body → 200400409500401403410
GET
/api/clients/{clientId}/secrets
Returns all secrets from the client
GetClientSecrets 4 params → 200404401403500410
DELETE
/api/clients/{clientId}/secrets/{secretId}
Removes an existing secret from the client
DeleteClientSecret 3 params → 200404401403500410
GET
/api/clients/{clientId}/secrets/{secretId}
Returns the secret by id from the client
GetClientSecretById 3 params → 200400404500401403410
GET
/api/scopes
Returns all scopes
GetScopes 1 param → 200401403500410

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are ClientApiDto (6 properties), SecretDto (6 properties), CreateClientDto (3 properties), ServiceResponseMessage (3 properties). Each schema is shown below with its type and property counts.

ServiceResponseMessage
object
3 properties
CreateClientDtoServiceRequest
object
1 property
CreateClientSecretDto
object
Represents client secret.
2 properties
ServiceResponse
object
2 properties
PatchClientDtoServiceRequest
object
1 property
CreatedClientSecretDtoServiceResponse
object
2 properties
PatchClientDto
object
Represents the data transfer object for patching a client (PATCH).
3 properties 1 required
CreateClientDto
object
Represents the data transfer object for creating a client.
3 properties 3 required
CreateClientSecretDtoServiceRequest
object
1 property
StringServiceResponse
object
2 properties
CreatedClientSecretDto
object
2 properties
ClientCreatedDto
object
Represents the data transfer object for a client created.
1 property 1 required
ClientCreatedDtoServiceResponse
object
2 properties
ObjectServiceResponse
object
2 properties
ClientSecretsDto
object
Represents the data transfer object for client secrets.
3 properties
ClientApiDtoServiceResponse
object
2 properties
ScopesDto
object
Represents the data transfer object for a scope.
1 property
ClientApiDto
object
Represents the data transfer object for a client.
6 properties 6 required
ClientApiDtoIEnumerableServiceResponse
object
2 properties
SecretDto
object
Represents the data transfer object for a client secret.
6 properties
ClientSecretsDtoServiceResponse
object
2 properties
SecretTypeDTO
string
SecretDtoServiceResponse
object
2 properties
ScopesDtoServiceResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-clients-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 Clients 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.