**Source URL:** https://limited.veevavault.dev/commercial/vault-api/api-reference/24.2/object-lifecycle-workflows/multi-record-workflows/retrieve-all-multi-record-workflows.md

# Retrieve All Multi-Record Workflows



Retrieve all available multi-record workflows which:

* The authenticated user has permissions to view or initiate

* Can be initiated through the API

<Endpoint path="/api/{version}/objects/objectworkflows/actions" method="GET"></Endpoint>

## Headers {#headers}

<FieldTable>
| Name | Description |
| --- | --- |
| `Accept` | `application/json` (default) or `application/xml` |
</FieldTable>

## Request {#request}

<CodeExample title="">
```
curl -X GET -H "Authorization: {SESSION_ID}" \
https://myvault.veevavault.com/api/v22.3/objects/objectworkflows/actions

```
</CodeExample>

## Response {#response}

<CodeExample title="">
```
{
   "responseStatus": "SUCCESS",
   "data": [
       {
           "name": "Objectworkflow.approval__c",
           "label": "Review & Approval Workflow",
           "type": "multirecordworkflow",
           "cardinality": "OneOrMany"
       }
   ]
}


```
</CodeExample>

## Response Details {#response-details}

On `SUCCESS`, the response includes the following:

<FieldTable>
| Name | Description |
| --- | --- |
| `name` | The workflow name. |
| `label` | UI label for the workflow. |
| `type` | Type of workflow. |
| `cardinality` | Indicates how many contents (`One`, `OneOrMany`) can be included in a workflow. |
</FieldTable>
For users without the *Workflow: Start* permission, the response returns an `INSUFFICIENT_ACCESS` error.



---

**Previous:** [Multi-Record Workflows](/commercial/vault-api/api-reference/24.2/object-lifecycle-workflows/multi-record-workflows)  
**Next:** [Retrieve Multi-Record Workflow Details](/commercial/vault-api/api-reference/24.2/object-lifecycle-workflows/multi-record-workflows/retrieve-multi-record-workflow-details)