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 Report Branding API

The ReportBranding API from Fenergo — 2 operation(s) for reportbranding.

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

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

This API exposes 4 operations across 2 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against 2 base URLs: /reportscommand, /reportsquery.

4 operations 2 paths 27 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.fenergox.com/advanceddashboardcommand
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Fenergo Report Branding 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 4

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

ReportBranding 4
PUT
/api/v2/report-branding
Configure report branding
ConfigureReportBranding 1 param body → 202400401403500410
DELETE
/api/v2/report-branding
Reset report branding
ResetReportBranding 1 param → 204400401403500410
GET
/api/v2/report-branding
Get report branding configuration
GetReportBranding 1 param → 200400401403500410
POST
/api/v2/report-branding/logo
Upload a tenant report branding logo
UploadLogo 1 param body → 200400401403500410

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are ReportBrandingResponseDto (6 properties), EmailConfigResponseDto (5 properties), ConfigureReportBrandingDto (5 properties), EmailConfigDto (5 properties). Each schema is shown below with its type and property counts.

ConfigureReportBrandingDtoServiceRequest
object
1 property
ValidationErrorModelListServiceResponse
object
2 properties
CoverSheetDto
object
Configuration for the cover sheet injected into XLSX reports.
3 properties
ServiceResponseMessage
object
3 properties
HeaderRowDto
object
Configuration for the header row styling in XLSX reports.
4 properties
ConfigureReportBrandingDto
object
Request payload for configuring tenant-level report branding.
5 properties
GuidServiceResponse
object
2 properties
DisclaimerDto
object
Configuration for the disclaimer block appended to XLSX reports.
2 properties
EmailConfigDto
object
Email-specific branding configuration applied to report notification emails.
5 properties
LogoDto
object
Represents the logo asset associated with tenant report branding.
4 properties
StringServiceResponse
object
2 properties
ValidationErrorModel
object
4 properties
XlsxConfigDto
object
Top-level XLSX-specific branding configuration.
3 properties
EmailFooterDto
object
Configuration for the footer block appended to report notification emails.
2 properties
UploadLogoResponseDto
object
Response payload returned after a logo file has been successfully uploaded to S3.
3 properties
UploadLogoResponseDtoServiceResponse
object
2 properties
ObjectServiceResponse
object
2 properties
EmailConfigResponseDto
object
Email-specific branding configuration applied to report notification emails.
5 properties
ReportBrandingResponseDto
object
Response payload representing the current tenant report branding configuration.
6 properties
ServiceResponse
object
2 properties
DisclaimerResponseDto
object
Configuration for the disclaimer block appended to XLSX reports.
2 properties
CoverSheetResponseDto
object
Configuration for the cover sheet injected into XLSX reports.
3 properties
EmailFooterResponseDto
object
Configuration for the footer block appended to report notification emails.
2 properties
XlsxConfigResponseDto
object
Top-level XLSX-specific branding configuration.
3 properties
LogoResponseDto
object
Represents the logo asset associated with tenant report branding.
4 properties
HeaderRowResponseDto
object
Configuration for the header row styling in XLSX reports.
4 properties
ReportBrandingResponseDtoServiceResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-reportbranding-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 Report Branding 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.