Skip to main content
GET
Get the result of a specific execution by its executionId

Authorizations

api_key
string
header
required

Headers

api_key
string
required

Your API key provided by FrankieOne

Example:

"245c765b124a098d09ef8765...."

X-Frankie-CustomerID
string
required

Your Customer ID provided by FrankieOne

Example:

"12345678-1234-1234-1234-123456789012"

X-Frankie-CustomerChildID
string

Your Customer Child ID provided by FrankieOne

Example:

"87654321-4321-4321-4321-210987654321"

X-Frankie-Channel
string

Open string that can be used to define the "channel" the request comes in from. It can potentially be used in routing and risk calculations upon request. Default values that can be used are: api portal smartui Any alphanumeric string is supported though. Anything over 64 characters will be truncated.

X-Frankie-Username
string

Username provided by API caller

Example:

"fred.flintstone@frankieone.com"

Path Parameters

entityId
string
required

Unique FrankieOne identifier for an entity

serviceName
string
required

The unique name of the service profile

workflowName
string
required

The unique name of the workflow

workflowExecutionId
string
required

Unique workflow execution identifier

Response

Workflow has completed

requestId
string

The unique request identifier for the API call made.

Example:

"01HN9XHZN6MGXM9JXG50K59Q85"

workflowResult
object

Summary of the workflow execution.

Using and interpreting the status field

The result of the workflow is represented in the status field. Users can manually override this status with a different value to change the outcome of the workflow. When the status field is overridden, the statusOverrideRequestId field is populated with the request ID of the override request. If the statusOverrideRequestId field is present and non-empty, it indicates that the status has been manually changed.

  1. Initial State:
    • When a workflow completes, its result is set in the status field.
  2. Status Override:
    • Users may override the status field with a different value (e.g., change FAIL to PASS).
  3. Identifying Overrides:
    • To determine if a status has been overridden, check for the presence of the statusOverrideRequestId field.
    • If present, it indicates that the status has been manually changed.
  4. Additional Override Information:
    • statusOverrideBy: Identifies the user who performed the override (may not always be present).
    • statusOverrideAt: Timestamp of when the override occurred.
  5. Interpretation:
    • If statusOverrideRequestId is empty or absent, no override has occurred.
    • If statusOverrideRequestId is present, then a manual override has occurred.
organization
object

Organization details at the current time. This could be different from the original organization details at the time of workflow execution.