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

The Document API from Fenergo — 7 operation(s) for document.

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

Tagged areas include Documents. 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, and defines 30 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 4 base URLs: /docgenquery, /externaldatacommand, /externaldataquery, /policyagent.

7 operations 7 paths 30 schemas 4 GET3 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 Document 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 7

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

Document 7
GET
/api/document/{id}
Get document by Id
GetDocumentById 2 params → 200400404401403500410
GET
/api/document/{journeyId}/{taskId}
Get documents by journey Id and task Id
GetDocumentsByJourneyIdTaskId 3 params → 200400404401403500410
POST
/api/documentdeprecated
Create new document retrieval request
postApiDocument 1 param body → 202400401403500410
POST
/api/document/saveDocumentsStatusesdeprecated
Reject/Reset documents status
postApiDocumentSaveDocumentsStatuses 1 param body → 202400401403500410
GET
/api/document/signedurl/{fileName}
Method to get a signed URL from S3
getApiDocumentSignedurlByFileName 2 params → 200400404401403500410
GET
/api/v1/document/{extractionId}/{documentId}/download
Download Policy Document
getApiV1DocumentByExtractionIdByDocumentIdDownload 3 params → 400200404403401500
POST
/api/v1/document
Upload Policy Document
postApiV1Document 1 param body → 400401403404409500200

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are DocumentModelDto (13 properties), HttpValidationProblemDetails (6 properties), DocumentRequestDataDto (6 properties), ValidationErrorModel (4 properties). Each schema is shown below with its type and property counts.

ValidationErrorModelListServiceResponse
object
2 properties
ServiceResponseMessage
object
3 properties
DocumentModelDto
object
13 properties
DocumentModelDtoIEnumerableServiceResponse
object
2 properties
StringServiceResponse
object
2 properties
ValidationErrorModel
object
4 properties
ObjectServiceResponse
object
2 properties
DocumentStatusRequestDto
object
2 properties 1 required
DocumentRequestCreatedDtoServiceResponse
object
Service response data
2 properties
ServiceResponseMessage_2
object
The message associated to the service response
3 properties
DocumentRequestCreatedDto
object
Response DTO representing the created Search request
1 property
ServiceResponse
object
Service response data
2 properties
StringServiceResponse_2
object
Service response data
2 properties
DocumentRequestDataDto
object
6 properties
DocumentRequestDtoServiceRequest
object
Service request data
1 property
DocumentRequestDto
object
2 properties 1 required
AccessLayerDto
object
DTO representing access layers attached
2 properties
DocumentStatusRequestDtoServiceRequest
object
Service request data
1 property
DocumentStatusRequestDataDto
object
2 properties
ObjectServiceResponse_2
object
Service response data
2 properties
ServiceResponse_2
object
Service response data
2 properties
StringServiceResponse_3
object
Service response data
2 properties
ServiceResponseMessage_3
object
The message associated to the service response
3 properties
ObjectServiceResponse_3
object
Service response data
2 properties
DownloadDocumentResponse
object
1 property
ServiceResponseMessage_4
object
The message associated to the service response
3 properties
UploadDocumentRequest
object
2 properties
UploadDocumentResponse
object
2 properties
HttpValidationProblemDetails
object
6 properties
ObjectServiceResponse_4
object
Service response data
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-document-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 Document 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.