IRironcladapp
Workflows

List All Workflow IDs

Changed on

Returns only the identifiers of the workflows you can access, without workflow bodies, schemas, or attributes. Use this to determine which workflows are visible to your credentials without paying the cost of a full workflow listing.

Filtering and pagination behave the same as List All Workflows. Because each result contains only identifiers, pageSize may be set as high as 10000.

Results are always ordered by when the workflow was last updated; sortDirection controls only the direction.

This endpoint reflects indexed workflow visibility and does not load each workflow individually, so in rare cases it may list a workflow whose full representation is temporarily unavailable from List All Workflows.

OAuth Scope required: public.workflows.readWorkflows

get/workflows/ids

Request

  • Base URL
    https://ironcladapp.com/public/api/v1
  • URL
    https://ironcladapp.com/public/api/v1/workflows/ids
  • Auth
    API key in header Authorization and OAuth 2
    Authorization code: https://ironcladapp.com/oauth/authorize
    Client credentials
    Token URL: https://ironcladapp.com/oauth/token scopes: public.workflows.readWorkflows

Query parameters

pageinteger

The page number used when paginating through a list of results.

pageSizeinteger

A limit of the number of results to return. The identifier-only endpoints return a small, fixed amount of data per result, so they support a much larger page size than the corresponding list endpoints.

string
OR
string[]
Example:active,completed

Filter the workflows that are listed based on their status. If this parameter is omitted, active workflows will be returned. Active workflows include workflows in the Create, Review, Sign, and Archive stages. To get workflows in more than one status, pass a comma-separated list (status=active,completed) or repeat the parameter (status=active&status=completed). Supported statuses: active, paused, completed, cancelled.

templatestring

Filter workflows to a specific Template ID.

sortDirection'ASC' | 'DESC'

The direction to sort by. Default is 'DESC'.

lastUpdatedstring

Retrieve workflows that have been updated since a UTC date.

filterstring

Filter workflows using a formula. The workflow attribute ID should be enclosed in brackets [ ] and the value should be enclosed in single quotes ' '.

Workflow attributes for a specific workflow design can be identified using the List All Workflow Schemas endpoint.

Supported formula operations include the following with documentation found here:

<ul> <li>Equals / NotEqual</li> <li>Contains</li> <li>IsEmpty / IsNotEmpty</li> <li>LessThan / LessThanOrEqual</li> <li>GreaterThan / GreaterThanOrEqual</li> <li>Date / Today / RelativeDate</li> <li>And / Or</li> </ul>
searchstring

Free-text search across all workflow properties, matching the in-app search. Combined with filter and any other parameters using logical AND. Maximum 1000 characters.

Headers

x-as-user-emailstring
Example:jane.doe@test.com

Denotes the actor of the request. When used, the API will take into account this user's permissions and access. This or x-as-user-id is required when the associated token was produced from the Client Credentials grant or with legacy bearer tokens on select endpoints. A token produced from the Authorization Code grant (which is already scoped to a user) may also use this header to act as a different user in the same company, provided the token carries the identity.users.impersonate scope and the token's own user has been granted the API User Impersonation permission. A request that sends this header without both never acts as the named user; depending on the company's configuration it either proceeds as the token's own user or is rejected with a 403. More information about permissions.

x-as-user-idstring
Example:5f0375c4cdc1927a3c5edcd3

Denotes the actor of the request. When used, the API will take into account this user's permissions and access. This or x-as-user-email is required when the associated token was produced from the Client Credentials grant or with legacy bearer tokens on select endpoints. A token produced from the Authorization Code grant (which is already scoped to a user) may also use this header to act as a different user in the same company, provided the token carries the identity.users.impersonate scope and the token's own user has been granted the API User Impersonation permission. A request that sends this header without both never acts as the named user; depending on the company's configuration it either proceeds as the token's own user or is rejected with a 403. More information about permissions.

Response

200

pageinteger
pageSizeinteger
countinteger

Example response

{
  "pageSize": 10000,
  "count": 12345,
  "list": [
    {
      "id": "22e2ff72-56a1-4711-a4ca-41328d311e9f",
      "ironcladId": "CONTRACT-123"
    }
  ]
}

Changes