PROCESIO API Documentation
How to call the PROCESIO REST API: where the full endpoint reference is, how to authenticate, which headers to send and how paged lists behave.
The PROCESIO REST API lets any other application work with PROCESIO: run a process, read its status and output, manage processes, Data Store tables, forms, credentials, schedules, webhooks and more.
The endpoint reference
The full, current list of endpoints, with their parameters, request bodies and responses, is in the interactive API reference (Swagger):
https://webapi.procesio.app/swagger/index.html
The reference is generated from the API itself, so it always matches what the API accepts. You can also try calls from it: click Authorize at the top right, sign in with one of the methods below, then open an endpoint and click Try it out.
The base URL for API calls is https://webapi.procesio.app. If your company runs its own PROCESIO installation, use the API address of that installation instead.
Authenticate
Every call needs one of these two credentials.
With an API key
An API key is the simplest choice for apps and scripts. Create one on the API Key page (see API Keys) and send it in two headers:
| Header | Value |
|---|---|
key | The key handle. |
value | The key value. |
A key works only in the workspace where it was created. In Swagger, use the KeyName and KeyValue boxes of the Authorize window.

With an access token
You can also sign in with a PROCESIO user and send the access token you get back.
- Send
POST /api/Authenticationwith these form fields (application/x-www-form-urlencoded):username: the user's email address.password: the user's password.code: the code from the authenticator app. Send it only when the user has two-factor authentication turned on.
- Send the access token from the response in the
Authorizationheader of your next calls:Authorization: Bearer <access token>.
The sign-in call can answer with:
| Status | Meaning |
|---|---|
200 | Signed in. The response carries the access token. |
401 | The sign-in was refused, for example because the email address or password is wrong. |
423 | The account is locked for a while after too many failed sign-ins. retryAfterSeconds says how long to wait, counted from the moment you got the answer. 0 means the wait is not known. Do not retry at once. |
428 | The user has two-factor authentication turned on. Send the request again with code. |
In Swagger, paste Bearer <access token> into the Bearer box of the Authorize window.

Headers
| Header | When to send it |
|---|---|
workspaceId | The ID of the workspace the call works in. Leave it out to work in your personal workspace. With an API key, send the ID of the workspace where you created the key. |
x-version | Optional. If you send it, its value must be 1.19. Requests without it work as before. |
Paged lists
Endpoints that return a list page by page take two query parameters, pageNumber and pageItemCount, and answer with:
| Field | What it holds |
|---|---|
pageItems | The items on this page. |
pageNumber | The page you got back. |
pageItemCount | The page size. |
totalItemCount | The number of items in the whole list. |
How out-of-range values behave:
- A
pageNumberpast the end of the list returns the last page, not an empty one.pageNumberin the response tells you which page you got. - A
pageNumberof0or less returns the first page. - A
pageItemCountof0or less returns the whole list in one page.
To read a whole list, stop when you have read totalItemCount items. Do not wait for an empty page: past the end, the API keeps returning the last page.
Example: run a process with an API key
This example runs a process from Postman. You need an API key and the ID of the process.
- Create a
POSTrequest tohttps://webapi.procesio.app/api/Projects/<process ID>/run. - Under Headers, add
key,valueand, for a process in a shared workspace,workspaceId. - Under Body, choose raw and JSON, and send the process inputs in
payload:
{
"payload": {
"inputVariableExample": 2.03
},
"connectionId": null
}
- Click Send. The process starts.
For a step-by-step version, see Running a process with API Keys. To follow the run, call GET /api/Projects/instances/<instance ID>/status. The other run endpoints are in the ProcessInstance group of the API reference.
OnPrem Agent v1.0.3
Install the OnPrem Agent on a Windows or Linux machine and run commands on it from a PROCESIO process with the OnPrem Agent CMD and Get Result actions.
PROCESIO SDK ~ Integrating with PROCESIO
To come to the aid of the community of developers who use PROCESIO in their applications we released a SDK that will help them get started. The…

