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 Scoped Entity API

The ScopedEntity API from Fenergo — 7 operation(s) for scopedentity.

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

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

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

Requests are made against 2 base URLs: /screeningcommand, /screeningquery.

10 operations 7 paths 13 schemas 4 GET3 POST3 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 Scoped Entity 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 7 paths, the API surfaces 10 operations — 4 GET, 3 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

ScopedEntity 10
POST
/api/scoped-entity
Adds new scoped entities to a given Journey and Process
AddScopedEntities 1 param body → 202400500401403410
PUT
/api/scoped-entity
Updates the entities that are in scope for Screening
UpdateScopedEntities 1 param body → 202400500401403410
POST
/api/v2/scoped-entity
Adds new scoped entities to a given Journey and Process
postApiV2ScopedEntity 1 param body → 202400500401403410
PUT
/api/v2/scoped-entity
Updates the entities that are in scope for Screening
putApiV2ScopedEntity 1 param body → 202400500401403410
POST
/api/v3/scoped-entity
Adds new scoped entities to a given Journey and Process
postApiV3ScopedEntity 1 param body → 202400500401403410
PUT
/api/v3/scoped-entity
Updates the entities that are in scope for Screening
putApiV3ScopedEntity 1 param body → 202400500401403410
GET
/api/scoped-entity/journey/{journeyId}/process/{processId}
Get all entities in scope for Screening for a given Journey and Process
GetScopedEntitiesByJourneyAndProcessId 3 params → 200400404500401403410
GET
/api/v2/scoped-entity/journey/{journeyId}/process/{processId}
Get all entities in scope for Screening for a given Journey and Process
getApiV2ScopedEntityJourneyByJourneyIdProcessByProcessId 3 params → 200400404500401403410
GET
/api/v3/scoped-entity/journey/{journeyId}/process/{processId}
Get all entities in scope for Screening for a given Journey and Process
getApiV3ScopedEntityJourneyByJourneyIdProcessByProcessId 3 params → 200400404500401403410
GET
/api/v4/scoped-entity/journey/{journeyId}/process/{processId}
Get all entities in scope for Screening for a given Journey and Process
getApiV4ScopedEntityJourneyByJourneyIdProcessByProcessId 3 params → 200400404500401403410

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are ScopedEntityDto (6 properties), AddScopedEntityResponseDto (4 properties), AddScopedEntitiesToJourneyProcessDto (3 properties), ServiceResponseMessage (3 properties). Each schema is shown below with its type and property counts.

ServiceResponseMessage
object
3 properties
AddScopedEntityResponseDtoIEnumerableServiceResponse
object
2 properties
ServiceResponse
object
2 properties
AddScopedEntitiesToJourneyProcessDto
object
Represents the AddScopedEntitiesToJourneyProcess request
3 properties
AddScopedEntityResponseDto
object
Represents the AddScopedEntitiesToJourneyProcess response
4 properties
UpdateScopedEntityDto
object
Represents the scoped entity in the UpdateScopedEntities request
2 properties
StringServiceResponse
object
2 properties
UpdateScopedEntityDtoListServiceRequest
object
1 property
AddScopedEntitiesToJourneyProcessDtoServiceRequest
object
1 property
AddScopedEntityDto
object
Represents the scoped entity in the AddScopedEntitiesToJourneyProcess request
2 properties
ObjectServiceResponse
object
2 properties
ScopedEntityDto
object
Represents Scoped Entity
6 properties 3 required
ScopedEntityDtoIEnumerableServiceResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-scopedentity-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 Scoped Entity 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.