Approval Flows

The approval flow defines how approvals can be conducted, including the number of approvers required, if approvals are needed before changes are implemented or as a post verification step, and in the cases of dual approval if they can take place in parallel or should be sequential.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required
length between 1 and 32

Unique name for the Approval Flow

string
required
length ≥ 1

A short description of the approval flow.

string | null

Miscellaneous notes and information for the entry or record.

string
required
length between 1 and 450

The approval strategy. This can be either approvals being required prior to implementation, or, as a post implementation verification.

string
required
length between 1 and 450

The approval principle can be either 'single' (4 eyes) or dual (6 eyes).

boolean

When the parallel option is checked, then the approvals can be conducted in parallel as opposed to sequential approvals.

Headers
string
enum
Defaults to application/json;odata.metadata=minimal;odata.streaming=true

Generated from available request content types

Response
200

OK

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here!