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

The DocumentRequirementMetadata API from Fenergo — 17 operation(s) for documentrequirementmetadata.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

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

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

28 operations 17 paths 41 schemas 6 DELETE4 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 Document Requirement Metadata 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 28

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

DocumentRequirementMetadata 28
POST
/api/documentrequirementmetadata/set
Create a document requirement metadata set model
CreateDocumentRequirementMetadataSet 1 param → 202400500401403410
GET
/api/documentrequirementmetadata/set
Gets the default Document Requirement Metadata Set of the tenant
GetDefaultDocumentRequirementMetadataSet 1 param → 200400404500401403410
POST
/api/documentrequirementmetadata/set/{setId}/version/{versionNumber}
Create document requirement metadata set version by version number
CreateDocumentRequirementMetadataSetVersionByVersionNumber 3 params → 202400404500401403410
PUT
/api/documentrequirementmetadata/set/{setId}/version/{versionNumber}
Update document requirement metadata set version
UpdateDocumentRequirementMetadataSetVersion 3 params body → 202400404409500401403410
DELETE
/api/documentrequirementmetadata/set/{setId}/version/{versionNumber}
Delete document requirement metadata set version
DeleteDocumentRequirementMetadataSetVersion 3 params → 202400404500401403410
GET
/api/documentrequirementmetadata/set/{setId}/version/{versionNumber}
Gets a Document Requirement Metadata Set Version by setId and version number
GetDocumentRequirementMetadataSetVersion 3 params → 200400404500401403410
POST
/api/documentrequirementmetadata/set/{setId}
Create document requirement metadata set version with given document…
CreateDocumentRequirementMetadataSetVersion 2 params body → 202400404500401403410
DELETE
/api/documentrequirementmetadata/set/{setId}
Delete document requirement metadata set and all its versions
DeleteDocumentRequirementMetadataSet 2 params → 202400404500401403410
PUT
/api/documentrequirementmetadata/set/{setId}/version/{versionNumber}/submit-for-approval
Submit document requirement metadata set version for approval
SubmitForApprovalDocumentRequirementMetadataSetVersion 3 params → 202400404500401403410
PUT
/api/documentrequirementmetadata/set/{setId}/version/{versionNumber}/sign
Sign document requirement metadata set version
SignDocumentRequirementMetadataSetVersion 3 params body → 202400404500401403410
PUT
/api/documentrequirementmetadata/set/{setId}/version/{versionNumber}/archive
Archive document requirement metadata set version
ArchiveDocumentRequirementMetadataSetVersion 3 params → 202400404500401403410
POST
/api/documentrequirementmetadata/set/{setId}/version/{versionNumber}/documentRequirementMetadata
Create document requirement metadata model
CreateDocumentRequirementMetadata 3 params body → 202400404500401403410
PUT
/api/documentrequirementmetadata/set/{setId}/version/{versionNumber}/documentRequirementMetadata/{id}
Update an existing document requirement metadata model
UpdateDocumentRequirementMetadata 4 params body → 202400404500401403410
DELETE
/api/documentrequirementmetadata/set/{setId}/version/{versionNumber}/documentRequirementMetadata/{id}
Delete an existing document requirement metadata model
DeleteDocumentRequirementMetadata 4 params → 202400404500401403410
GET
/api/documentrequirementmetadata/set/{setId}/version/{versionNumber}/documentRequirementMetadata/{id}
Gets a Document Requirement Metadata by Id
GetDocumentRequirementMetadataById 4 params → 200400404500401403410
POST
/api/v2/documentrequirementmetadata/set
Create a document requirement metadata set model
postApiV2DocumentrequirementmetadataSet 1 param → 202400500401403410
POST
/api/v2/documentrequirementmetadata/set/{setId}/version/{versionNumber}
Create document requirement metadata set version by version number
postApiV2DocumentrequirementmetadataSetBySetIdVersionByVersionNumber 3 params → 202400404500401403410
PUT
/api/v2/documentrequirementmetadata/set/{setId}/version/{versionNumber}
Update document requirement metadata set version
putApiV2DocumentrequirementmetadataSetBySetIdVersionByVersionNumber 3 params body → 202400404409500401403410
DELETE
/api/v2/documentrequirementmetadata/set/{setId}/version/{versionNumber}
Delete document requirement metadata set version
deleteApiV2DocumentrequirementmetadataSetBySetIdVersionByVersionNumber 3 params → 202400404500401403410
POST
/api/v2/documentrequirementmetadata/set/{setId}
Create document requirement metadata set version with given document…
postApiV2DocumentrequirementmetadataSetBySetId 2 params body → 202400404500401403410
DELETE
/api/v2/documentrequirementmetadata/set/{setId}
Delete document requirement metadata set and all its versions
deleteApiV2DocumentrequirementmetadataSetBySetId 2 params → 202400404500401403410
PUT
/api/v2/documentrequirementmetadata/set/{setId}/version/{versionNumber}/submit-for-approval
Submit document requirement metadata set version for approval
putApiV2DocumentrequirementmetadataSetBySetIdVersionByVersionNumberSubmitForApproval 3 params → 202400404500401403410
PUT
/api/v2/documentrequirementmetadata/set/{setId}/version/{versionNumber}/sign
Sign document requirement metadata set version
putApiV2DocumentrequirementmetadataSetBySetIdVersionByVersionNumberSign 3 params body → 202400404500401403410
PUT
/api/v2/documentrequirementmetadata/set/{setId}/version/{versionNumber}/archive
Archive document requirement metadata set version
putApiV2DocumentrequirementmetadataSetBySetIdVersionByVersionNumberArchive 3 params → 202400404500401403410
POST
/api/v2/documentrequirementmetadata/set/{setId}/version/{versionNumber}/documentRequirementMetadata
Create document requirement metadata model
postApiV2DocumentrequirementmetadataSetBySetIdVersionByVersionNumberDocumentRequirementMetadata 3 params body → 202400404500401403410
PUT
/api/v2/documentrequirementmetadata/set/{setId}/version/{versionNumber}/documentRequirementMetadata/{id}
Update an existing document requirement metadata model
putApiV2DocumentrequirementmetadataSetBySetIdVersionByVersionNumberDocumentRequirementMetadataById 4 params body → 202400404500401403410
DELETE
/api/v2/documentrequirementmetadata/set/{setId}/version/{versionNumber}/documentRequirementMetadata/{id}
Delete an existing document requirement metadata model
deleteApiV2DocumentrequirementmetadataSetBySetIdVersionByVersionNumberDocumentRequirementMetadataById 4 params → 202400404500401403410
GET
/api/documentrequirementmetadata
Gets all Document Requirement Metadata
GetLatestDocumentRequirementMetadata 1 param → 200400500401403410

Schemas 41

The contract defines 41 schemas that model the data the API accepts and returns. The most detailed are ValidationDataDto (13 properties), ValidationDataDto_2 (13 properties), DocumentRequirementMetadataSetVersionDto (12 properties), DocumentRequirementMetadataDto_2 (10 properties). Each schema is shown below with its type and property counts.

ServiceResponseMessage
object
3 properties
RegexRuleDto
object
4 properties
CreateDocReqMetadataResponseDtoServiceResponse
object
2 properties
CreateDocReqMetadataSetVersionDto
object
Request DTO representing set of properties which define a new version of DocumentRequirementMetadata set
3 properties
BaseDocumentRequirementMetadataDtoServiceRequest
object
1 property
StringServiceResponse
object
2 properties
Approver
object
4 properties
CreateDocReqMetadataSetVersionDtoServiceRequest
object
1 property
UpdateDocReqMetadataSetVersionDto
object
Request DTO representing set of properties which define a new version of DocumentRequirementMetadata set
3 properties
ObjectServiceResponse
object
2 properties
ValidationDataDto
object
13 properties
ServiceResponse
object
2 properties
CreateDocReqMetadataSetResponseDtoServiceResponse
object
2 properties
Decision
string
CreateDocReqMetadataResponseDto
object
Response DTO representing Document Requirement Metadata Set Version data
1 property
BasicRuleDto
object
2 properties
Signee
object
4 properties
BaseDocumentRequirementMetadataDto
object
7 properties
UpdateDocReqMetadataSetVersionDtoServiceRequest
object
1 property
SpecialCharactersRuleDto
object
3 properties
ApproveAction
object
3 properties
ValueLimitRuleDto
object
4 properties
CreateDocReqMetadataSetResponseDto
object
Response DTO representing Document Requirement Metadata Set Version data
2 properties
DocumentRequirementMetadataDto
object
8 properties
DateLimitRuleDto
object
4 properties
ApproveActionServiceRequest
object
1 property
DocumentRequirementMetadataDtoServiceRequest
object
1 property
RegexRuleDto_2
object
Request DTO representing regex rule metadata
4 properties
DocumentRequirementMetadataSetVersionDto
object
Response DTO representing Document Requirement Metadata Set Version data
12 properties
DocumentRequirementMetadataDtoIEnumerableServiceResponse
object
2 properties
ValidationDataDto_2
object
Request DTO representing validation data metadata
13 properties
DocumentRequirementMetadataSetVersionDtoServiceResponse
object
2 properties
BasicRuleDto_2
object
Request DTO representing basic validation rule metadata
2 properties
DocumentRequirementMetadataSetDtoServiceResponse
object
2 properties
SpecialCharactersRuleDto_2
object
Request DTO representing special characters rule metadata
3 properties
ValueLimitRuleDto_2
object
Request DTO representing value limit rule metadata
4 properties
DocumentRequirementMetadataDtoServiceResponse
object
2 properties
DocumentRequirementMetadataDto_2
object
Response DTO representing Document Requirement Metadata data
10 properties
VersionStatus
string
DateLimitRuleDto_2
object
Request DTO representing date limit rule metadata
4 properties
DocumentRequirementMetadataSetDto
object
Response DTO representing Document Requirement Metadata Set data
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-documentrequirementmetadata-api-openapi.yml Raw ↑

Other APIs Fenergo publishes across the network.

Fenergo Acceptable Document API
AE Profile APIs.io
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
#DocumentRequirementMetadata
← Back to F APIs
API Details
ID
fenergo:fenergo-documentrequirementmetadata-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-documentrequirementmetadata-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/fenergo-documentrequirementmetadata-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 Document Requirement Metadata 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.