For the complete documentation index, see llms.txt. This page is also available as Markdown.

Procurement | Approval Flows

get
Authorizations
X-API-KEYstringRequired

Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.

Query parameters
nameFilterstringOptional
Responses
200

OK

application/json

Data transfer for an approval flow. Maps also to the [flow] entity of the appmixer service.

flowIdstring · nullableOptional
templateIdstring · uuidOptional
typestring · enumOptional

The type of approval flow. Simple approval flows are predefined flows which can be used out of the box. Custom approval flows are flows which can be customized by the user. Default approval flows are the default flows that are used when no other flow is specified.

Possible values:
stagestring · enumOptional

Indicates the stage of the approval flow. This represents the state of the flow in appmixer.

Possible values:
titlestring · nullableOptional
startedstring · date-timeOptional
createdstring · date-timeOptional
modifiedstring · date-timeOptional
descriptionstring · nullableOptional
get/v1/procurement/approval-flow-templates
get
Authorizations
X-API-KEYstringRequired

Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.

Query parameters
flowTypeFilterstring · enumOptionalPossible values:
nameFilterstringOptional
Responses
200

OK

application/json

Resource list of configured approval flows for the tenant.

totalinteger · int32Optional

Total number of configured approval flows.

get/v1/procurement/approval-flows
post
Authorizations
X-API-KEYstringRequired

Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.

Body
flowIdstring · nullableOptional
namestring · nullableOptional
descriptionstring · nullableOptional
templateIdstring · nullableOptional
requireSameLevelApprovalbooleanOptional

When true, an approval request is created for the other same-level approvers even if the order creator is themselves one of the approvers. When false (default), the order is auto-approved with no request in that case.

Responses
200

OK

application/json

Data transfer for an approval flow. Maps also to the [flow] entity of the appmixer service.

flowIdstring · nullableOptional
templateIdstring · uuidOptional
typestring · enumOptional

The type of approval flow. Simple approval flows are predefined flows which can be used out of the box. Custom approval flows are flows which can be customized by the user. Default approval flows are the default flows that are used when no other flow is specified.

Possible values:
stagestring · enumOptional

Indicates the stage of the approval flow. This represents the state of the flow in appmixer.

Possible values:
titlestring · nullableOptional
startedstring · date-timeOptional
createdstring · date-timeOptional
modifiedstring · date-timeOptional
descriptionstring · nullableOptional
post/v1/procurement/approval-flows
delete
Authorizations
X-API-KEYstringRequired

Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.

Responses
204

No Content

No content

delete/v1/procurement/approval-flows

No content

Last updated

Was this helpful?