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 Journey Schedule API

The JourneySchedule API from Fenergo — 7 operation(s) for journeyschedule.

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

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

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

Requests are made against 2 base URLs: /journeycommand, /journeyquery.

12 operations 7 paths 30 schemas 2 DELETE3 GET3 POST4 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 Journey Schedule 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 12

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

JourneySchedule 12
POST
/api/journey-schedule
Create journey Schedule
CreateJourneySchedule 2 params body → 202400401403500410
GET
/api/journey-schedule
Get journey Schedules
GetAllJourneySchedules 1 param → 200400401403500410
POST
/api/journey-schedule/{journeyScheduleId}
Create journey Schedule version
CreateJourneyScheduleVersion 3 params body → 202404400401403500410
DELETE
/api/journey-schedule/{journeyScheduleId}
Delete journey Schedule and all its versions
DeleteJourneySchedule 3 params → 202404400401403500410
GET
/api/journey-schedule/{journeyScheduleId}
Get journey Schedule by id
GetJourneyScheduleById 2 params → 200404400401403500410
PUT
/api/journey-schedule/{journeyScheduleId}/version/{versionNumber}
Update journey Schedule version
UpdateJourneyScheduleVersion 4 params body → 202404409400401403500410
DELETE
/api/journey-schedule/{journeyScheduleId}/version/{versionNumber}
Delete journey Schedule version
DeleteJourneyScheduleVersion 4 params → 202404400401403500410
GET
/api/journey-schedule/{journeyScheduleId}/version/{versionNumber}
Get journey Schedule by id and version
GetJourneyScheduleVersionById 3 params → 200404400401403500410
POST
/api/journey-schedule/{journeyScheduleId}/version/{versionNumber}/clone
Clone journey Schedule version
CloneJourneyScheduleVersion 4 params body → 202404400401403500410
PUT
/api/journey-schedule/{journeyScheduleId}/version/{versionNumber}/submit-for-approval
Submit journey Schedule version for approval
SubmitJourneyScheduleVersion 4 params → 202404400401403500410
PUT
/api/journey-schedule/{journeyScheduleId}/version/{versionNumber}/sign
Sign journey Schedule version
SignJourneyScheduleVersion 4 params body → 202404400401403500410
PUT
/api/journey-schedule/{journeyScheduleId}/version/{versionNumber}/archive
Archive journey Schedule version
ArchiveJourneyScheduleVersion 4 params → 202400404401403500410

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are JourneyScheduleVersionDto (15 properties), JourneyScheduleDto (10 properties), ConditionDefinitionDto (9 properties), UpdateJourneyScheduleVersionDto (9 properties). Each schema is shown below with its type and property counts.

CloneJourneyScheduleVersionDto
object
Request DTO representing clone journey Schedule data
2 properties
ServiceResponseMessage
object
The message associated to the service response
3 properties
UpdateJourneyScheduleVersionDtoServiceRequest
object
Service request data
1 property
JourneyScheduleVersionSignResponseServiceResponse
object
Service response data
2 properties
StringServiceResponse
object
Service response data
2 properties
Approver
object
4 properties
ConditionDto
object
Represents condition root
5 properties 3 required
UpdateJourneyScheduleVersionDto
object
Request DTO representing set of properties which define a new version of journey Schedule
9 properties
ObjectServiceResponse
object
Service response data
2 properties
JourneyScheduleDtoServiceResponse
object
Service response data
2 properties
JourneyScheduleDtoServiceRequest
object
Service request data
1 property
JourneyScheduleDto
object
DTO representing journey Schedule data
10 properties 3 required
ValueField
object
2 properties
Decision
string
CloneJourneyScheduleVersionResponseServiceResponse
object
Service response data
2 properties
Signee
object
Defines a version Signee
4 properties
ValidationErrorModel
object
Represents the details of validation error
4 properties
ConditionDefinitionDto
object
Represents condition
9 properties
CloneJourneyScheduleVersionDtoServiceRequest
object
Service request data
1 property
ValidationErrorModelListServiceResponse
object
Service response data
2 properties
ApproveAction
object
3 properties
CloneJourneyScheduleVersionResponse
object
Cloned journey schedule response data
1 property
JourneyScheduleVersionSignResponse
object
Sign journey Schedule response contains the new version status
3 properties
VersionStatus
string
ApproveActionServiceRequest
object
Service request data
1 property
JourneyScheduleVersionDto
object
Response DTO representing journey Schedule version data
15 properties
JourneyScheduleDtoIEnumerableServiceResponse
object
Service response data
2 properties
JourneyScheduleVersionDtoServiceResponse
object
Service response data
2 properties
ConditionDto_2
object
Represents condition root
5 properties
JourneyScheduleDto_2
object
Response DTO representing journey Schedule data
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fenergo-journeyschedule-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 Journey Schedule 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.