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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Fenergo

Fenergo Acceptable Document API

The AcceptableDocument API from Fenergo — 19 operation(s) for acceptabledocument.

Documentation Provider Profile APIs.io OpenAPI GitHub

Fenergo Acceptable 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 AcceptableDocument. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against 2 base URLs: /documentmanagementcommand, /documentmanagementquery.

30 operations 19 paths 30 schemas 6 DELETE6 GET8 POST10 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 Acceptable 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 30

Across 19 paths, the API surfaces 30 operations — 6 DELETE, 6 GET, 8 POST, 10 PUT. Each is listed below with its method, path, parameters, and response codes.

AcceptableDocument 30
POST
/api/acceptabledocument/set
Create acceptable document set model
CreateAcceptableDocumentSet 1 param → 202400500401403410
GET
/api/acceptabledocument/set
Gets the default Acceptable Document Set of the tenant
GetDefaultAcceptableDocumentSet 1 param → 200400404500401403410
POST
/api/acceptabledocument/set/{setId}/version/{versionNumber}
Create acceptable document set version by version number
CreateAcceptableDocumentSetVersionByVersionNumber 3 params → 202400404500401403410
PUT
/api/acceptabledocument/set/{setId}/version/{versionNumber}
Update acceptable document set version
UpdateAcceptableDocumentSetVersion 3 params body → 202400404409500401403410
DELETE
/api/acceptabledocument/set/{setId}/version/{versionNumber}
Delete acceptable document set version
DeleteAcceptableDocumentSetVersion 3 params → 202400404500401403410
GET
/api/acceptabledocument/set/{setId}/version/{versionNumber}
Gets an Acceptable Document Set Version by setId and version number
GetAcceptableDocumentSetVersion 3 params → 200400404500401403410
POST
/api/acceptabledocument/set/{setId}
Create acceptable document set version with given acceptable documents
CreateAcceptableDocumentSetVersion 2 params body → 202400404500401403410
DELETE
/api/acceptabledocument/set/{setId}
Delete acceptable document set and all its versions
DeleteAcceptableDocumentSet 2 params → 202400404500401403410
PUT
/api/acceptabledocument/set/{setId}/version/{versionNumber}/submit-for-approval
Submit acceptable document set version for approval
SubmitForApprovalAcceptableDocumentSetVersion 3 params → 202400404500401403410
PUT
/api/acceptabledocument/set/{setId}/version/{versionNumber}/sign
Sign acceptable document set version
SignAcceptableDocumentSetVersion 3 params body → 202400404500401403410
PUT
/api/acceptabledocument/set/{setId}/version/{versionNumber}/archive
Archive acceptable document set version
ArchiveAcceptableDocumentSetVersion 3 params → 202400404500401403410
POST
/api/acceptabledocument/set/{setId}/version/{versionNumber}/acceptableDocument
Create acceptable document model
CreateAcceptableDocument 3 params body → 202400404500401403410
PUT
/api/acceptabledocument/set/{setId}/version/{versionNumber}/acceptableDocument/{id}
Update an existing acceptable document model
UpdateAcceptableDocument 4 params body → 202400404500401403410
DELETE
/api/acceptabledocument/set/{setId}/version/{versionNumber}/acceptableDocument/{id}
Delete an existing acceptable document model
DeleteAcceptableDocument 4 params → 202400404500401403410
GET
/api/acceptabledocument/set/{setId}/version/{versionNumber}/acceptableDocument/{id}
Gets an Acceptable Document by Id
GetAcceptableDocumentById 4 params → 200400404500401403410
POST
/api/v2/acceptabledocument/set
Create acceptable document set model
postApiV2AcceptabledocumentSet 1 param → 202400500401403410
POST
/api/v2/acceptabledocument/set/{setId}/version/{versionNumber}
Create acceptable document set version by version number
postApiV2AcceptabledocumentSetBySetIdVersionByVersionNumber 3 params → 202400404500401403410
PUT
/api/v2/acceptabledocument/set/{setId}/version/{versionNumber}
Update acceptable document set version
putApiV2AcceptabledocumentSetBySetIdVersionByVersionNumber 3 params body → 202400404409500401403410
DELETE
/api/v2/acceptabledocument/set/{setId}/version/{versionNumber}
Delete acceptable document set version
deleteApiV2AcceptabledocumentSetBySetIdVersionByVersionNumber 3 params → 202400404500401403410
POST
/api/v2/acceptabledocument/set/{setId}
Create acceptable document set version with given acceptable documents
postApiV2AcceptabledocumentSetBySetId 2 params body → 202400404500401403410
DELETE
/api/v2/acceptabledocument/set/{setId}
Delete acceptable document set and all its versions
deleteApiV2AcceptabledocumentSetBySetId 2 params → 202400404500401403410
PUT
/api/v2/acceptabledocument/set/{setId}/version/{versionNumber}/submit-for-approval
Submit acceptable document set version for approval
putApiV2AcceptabledocumentSetBySetIdVersionByVersionNumberSubmitForApproval 3 params → 202400404500401403410
PUT
/api/v2/acceptabledocument/set/{setId}/version/{versionNumber}/sign
Sign acceptable document set version
putApiV2AcceptabledocumentSetBySetIdVersionByVersionNumberSign 3 params body → 202400404500401403410
PUT
/api/v2/acceptabledocument/set/{setId}/version/{versionNumber}/archive
Archive acceptable document set version
putApiV2AcceptabledocumentSetBySetIdVersionByVersionNumberArchive 3 params → 202400404500401403410
POST
/api/v2/acceptabledocument/set/{setId}/version/{versionNumber}/acceptableDocument
Create acceptable document model
postApiV2AcceptabledocumentSetBySetIdVersionByVersionNumberAcceptableDocument 3 params body → 202400404500401403410
PUT
/api/v2/acceptabledocument/set/{setId}/version/{versionNumber}/acceptableDocument/{id}
Update an existing acceptable document model
putApiV2AcceptabledocumentSetBySetIdVersionByVersionNumberAcceptableDocumentById 4 params body → 202400404500401403410
DELETE
/api/v2/acceptabledocument/set/{setId}/version/{versionNumber}/acceptableDocument/{id}
Delete an existing acceptable document model
deleteApiV2AcceptabledocumentSetBySetIdVersionByVersionNumberAcceptableDocumentById 4 params → 202400404500401403410
GET
/api/acceptabledocument
Gets all Acceptable Documents
GetLatestAcceptableDocuments 1 param → 200400500401403410
GET
/api/acceptabledocument/set/metadata
Gets the default Acceptable Document Set Metadata of the tenant
GetDefaultAcceptableDocumentSetMetadata 1 param → 200400404500401403410
GET
/api/acceptabledocument/set/paged
Gets paged default Acceptable Document Set of the tenant
GetPagedDefaultAcceptableDocumentSet 3 params → 200400404500401403410

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are AcceptableDocumentSetVersionDto (12 properties), AcceptableDocumentDto_2 (8 properties), AcceptableDocumentDto (8 properties), CreateAcceptableDocumentRequestDto (7 properties). Each schema is shown below with its type and property counts.

ServiceResponseMessage
object
3 properties
CreateAcceptableDocumentSetResponseDtoServiceResponse
object
2 properties
StringServiceResponse
object
2 properties
Approver
object
4 properties
AcceptableDocumentDto
object
8 properties
AcceptableDocumentDtoServiceRequest
object
1 property
CreateAcceptableDocumentRequestDtoServiceRequest
object
1 property
ObjectServiceResponse
object
2 properties
CreateAcceptableDocumentSetVersionDto
object
Request DTO representing set of properties which define a new version of AcceptableDocument set
3 properties
UpdateAcceptableDocumentSetVersionDto
object
Request DTO representing set of properties which define a new version of AcceptableDocument set
3 properties
ServiceResponse
object
2 properties
UpdateAcceptableDocumentSetVersionDtoServiceRequest
object
1 property
Decision
string
Signee
object
4 properties
ApproveAction
object
3 properties
CreateAcceptableDocumentSetVersionDtoServiceRequest
object
1 property
CreateAcceptableDocumentSetResponseDto
object
Response DTO representing Acceptable Document Set Version data
2 properties
CreateAcceptableDocumentRequestDto
object
7 properties
AcceptableDocumentDtoServiceResponse
object
2 properties
ApproveActionServiceRequest
object
1 property
AcceptableDocumentSetVersionDto
object
Response DTO representing Acceptable Document Set Version data
12 properties
PagedAcceptableDocumentResponseDtoServiceResponse
object
2 properties
AcceptableDocumentSetDto
object
Response DTO representing Acceptable Document Set data
2 properties
AcceptableDocumentDtoIEnumerableServiceResponse
object
2 properties
PagedAcceptableDocumentResponseDto
object
2 properties
AcceptableDocumentDto_2
object
Response DTO representing Acceptable Document data
8 properties
VersionStatus
string
AcceptableDocumentDtoServiceResponse_2
object
2 properties
AcceptableDocumentSetVersionDtoServiceResponse
object
2 properties
AcceptableDocumentSetDtoServiceResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-acceptabledocument-api-openapi.yml Raw ↑

Other APIs Fenergo publishes across the network.

Fenergo Access Layer API
AE Profile APIs.io
Fenergo Adapter Mock API
AE Profile APIs.io
Fenergo Advanced Dashboard API
AE Profile APIs.io
Fenergo Agency API
AE Profile APIs.io
Fenergo Agent API
AE Profile APIs.io
Fenergo Agent Slos API
AE Profile APIs.io
Fenergo Agent Value Story API
AE Profile APIs.io
Fenergo Aggregation API
AE Profile APIs.io
Fenergo Allocation API
AE Profile APIs.io
Fenergo Allocation Configuration API
AE Profile APIs.io
Fenergo Asset API
AE Profile APIs.io
Fenergo Asset Draft API
AE Profile APIs.io
#AcceptableDocument
← Back to F APIs
API Details
ID
fenergo:fenergo-acceptabledocument-api
Base URL
https://api.fenergox.com/advanceddashboardcommand
Docs
https://docs.fenergox.com/api-docs/other-clm-apis/advanced-dashboard-api/advanced-dashboard-command
Provider
Fenergo
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=fenergo-acceptabledocument-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/fenergo-acceptabledocument-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Fenergo Acceptable 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.