Methods
The OpenProcess API enables third party/external applications to interact with the OpenProcess application.
The API is REST API driven and each method/endpoint is documented below. Where licensed these APIs can be tested using the actual Swagger UI endpoint in OpenProcess.
Gets a custom data extract. N.B. this is an optional component, currently licensed for OpenProcess point solutions such as Right to Buy.
post
Path parameters
fileDescriptorIdstringRequired
The id of the descriptor file. This defines the number and type of columns in the extract
Body
typeinteger · enumRead-onlyOptionalPossible values:
Responses
200
OK
Responseobject
post
POST /open-api/extracts/{fileDescriptorId} HTTP/1.1
Host: openprocess-test.ieg4.net
Content-Type: application/json
Accept: */*
Content-Length: 2
{}
200
OK
{}
Path parameters
processIdstringRequired
stepIdstringRequired
Body
Responses
200
OK
Responseobject
post
POST /open-api/processes/{processId}/steps/{stepId}/complete HTTP/1.1
Host: openprocess-test.ieg4.net
Content-Type: application/json
Accept: */*
Content-Length: 119
{
"fields": [
{
"fieldId": "text",
"code": "text",
"name": "text",
"description": "text",
"fieldType": "text",
"confidential": true
}
]
}
200
OK
{}
Path parameters
processIdstringRequired
Body
contentsstringOptional
visibleToAccountsbooleanOptional
Responses
200
OK
Responseobject
post
POST /open-api/processes/{processId}/notes HTTP/1.1
Host: openprocess-test.ieg4.net
Content-Type: application/json
Accept: */*
Content-Length: 44
{
"contents": "text",
"visibleToAccounts": true
}
200
OK
{}
Start a process
Last updated
Was this helpful?