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

The Localisation API from Fenergo — 12 operation(s) for localisation.

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

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

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

Requests are made against 2 base URLs: /localisationcommand, /localisationquery.

18 operations 12 paths 32 schemas 2 DELETE9 GET2 POST5 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 Localisation 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 18

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

Localisation 18
POST
/api/localisation
Create a new Localisation
CreateLocalisation 1 param body → 202400401403500410
GET
/api/localisation
Get all Localisations for the client tenant without Context data
GetAllLocalisations 1 param → 200400401403500410
PUT
/api/localisation/{localisationId}
Update Localisations Settings
UpdateLocalisation 2 params body → 202400404401403500410
DELETE
/api/localisation/{localisationId}
Delete Localisation and all it's versions
DeleteLocalisation 2 params → 202400404401403500410
POST
/api/localisation/{localisationId}
Create a new Version for an existing Localisation
CreateLocalisationVersion 2 params body → 202400404401403500410
GET
/api/localisation/{localisationId}
Get the active version of an existing Localisation by ID
GetLocalisationById 2 params → 200400404401403500410
PUT
/api/localisation/{localisationId}/version/{versionNumber}
Updates an existing Version of a Localisation
UpdateLocalisationVersion 3 params body → 202400404401403500410
DELETE
/api/localisation/{localisationId}/version/{versionNumber}
Delete an existing Version of a Localisation
DeleteLocalisationVersion 3 params → 202400404401403500410
GET
/api/localisation/{localisationId}/version/{versionNumber}
Get a specific version of an existing Localisation
GetLocalisationVersionById 3 params → 200400404401403500410
PUT
/api/localisation/{localisationId}/version/{versionNumber}/submit-for-approval
Submit an existing Version of a Localisation for Approval
SubmitLocalisationVersion 3 params → 202400404401403500410
PUT
/api/localisation/{localisationId}/version/{versionNumber}/sign
Sign an existing Version of a Localisation
SignLocalisationVersion 3 params body → 202400404401403500410
PUT
/api/localisation/{localisationId}/version/{versionNumber}/archive
Archive an existing Version of a Localisation
ArchiveLocalisationVersion 3 params → 202400404401403500410
GET
/api/localisation/active
Get all Localisations active version for the client tenant
GetAllActiveLocalisations 1 param → 200400401403500410
GET
/api/localisation/default
Get default localisation and language
GetDefaultLocalisation 1 param → 200400401403500410
GET
/api/localisation/{localisationId}/version/{versionNumber}/context/{contextName}
Get the context of a specific version for an existing Localisation
GetLocalisationContextByVersionAndContextName 4 params → 200400404401403500410
GET
/api/localisation/{localisationId}/version/{versionNumber}/context/{contextName}/signedUrl
Get Presigned Url of specific version of an existing Localisation context
GetLocalisationContextSignedUrlByVersionAndContextName 4 params → 200400404401403500410
GET
/api/localisation/systemLanguages
Get All Supported System Language Code
GetAllSystemLanguages 1 param → 200400404401403500410
GET
/api/localisation/systemLanguage/{languageCode}
Get Presigned Url and Last Updated time of specific System Language
GetSystemLanguageByLanguageCode 2 params → 200400404401403500410

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are LocalisationVersionDto (15 properties), LocalisationLiteVersionDto (15 properties), LocalisationDto (9 properties), UpdateLocalisationVersionDto (7 properties). Each schema is shown below with its type and property counts.

ServiceResponseMessage
object
3 properties
UpdateLocalisationVersionDto
object
Set of properties which define new version of Localisation
7 properties
StringServiceResponse
object
2 properties
Approver
object
4 properties
ObjectServiceResponse
object
2 properties
UpdateLocalisationVersionDtoServiceRequest
object
1 property
LocalisationVersionSignResponse
object
Contains the new version Status, after a version sign operation
3 properties
LocalisationDto
object
Localisation representation
9 properties
LocalisationDtoServiceRequest
object
1 property
LocalisationDtoServiceResponse
object
2 properties
Decision
string
Signee
object
4 properties
UpdateLocalisationDto
object
1 property
ValidationErrorModel
object
4 properties
ValidationErrorModelListServiceResponse
object
2 properties
LocalisationVersionSignResponseServiceResponse
object
2 properties
ApproveAction
object
3 properties
VersionStatus
string
ApproveActionServiceRequest
object
1 property
LocalisationLiteVersionDto
object
Instance of a Localisation Version.
15 properties
Approver_2
object
4 properties
StringIEnumerableServiceResponse
object
2 properties
SystemLanguageDto
object
Defines column with metadata for localisation values
3 properties
LocalisationDtoIEnumerableServiceResponse
object
2 properties
LocalisationVersionDto
object
Instance of a Localisation Version.
15 properties
LocalisationDto_2
object
Localisation Data
3 properties
Signee_2
object
4 properties
SystemLanguageDtoServiceResponse
object
2 properties
ApproveAction_2
object
3 properties
ContextDto
object
Defines column with metadata for localisation values
5 properties
LocalisationLiteVersionDtoServiceResponse
object
2 properties
LocalisationVersionDtoServiceResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-localisation-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 Localisation 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.