---
title: Create workflows using REST APIs
description: Identity Governance stores and saves workflow configurations in JSON format. You can manage the default workflow definitions for each access request type using REST APIs.
component: pingoneaic
page_id: pingoneaic:identity-governance:administration/workflow-create-rest
canonical_url: https://docs.pingidentity.com/pingoneaic/identity-governance/administration/workflow-create-rest.html
keywords: ["workflows", "REST API", "create workflow", "workflow definition", "json"]
section_ids:
  steps-manage-workflow-definition: Steps to manage workflow definitions using REST API
---

# Create workflows using REST APIs

Identity Governance stores and saves workflow configurations in JSON format. You can manage the default workflow definitions for each [access request type](workflow-configure.html#workflow-access-request-types) using REST APIs.

|   |                                                                                            |
| - | ------------------------------------------------------------------------------------------ |
|   | For an example of a JSON file, learn more in [Workflow use cases](workflow-examples.html). |

## Steps to manage workflow definitions using REST API

1. Retrieve the current default workflow configurations for access request types using `/auto/orchestration/definition`(GET).

   |   |                                                                                                                           |
   | - | ------------------------------------------------------------------------------------------------------------------------- |
   |   | Save a copy of the default workflow for the access request type in case of an error with your updated workflow JSON file. |

2. Modify the default workflow to suit your needs.

3. Create a new default workflow definition for an access request type in a `draft` state using `/auto/orchestration/definition?_action=create` (POST).

   Each access request type can *only* contain one workflow definition in the `draft` and `publish` states. One can exist in the `draft` state and the `publish` state.

4. Validate the workflow definition before publishing using `/auto/orchestration/definition?_action=validate` (POST).

5. Publish the workflow definition from its `draft` state using `/auto/orchestration/definition?_action=publish` (POST).

   |   |                                                               |
   | - | ------------------------------------------------------------- |
   |   | You can't delete workflow definitions in the published state. |

6. Repeat steps 1 - 5 for each access request type desired.

Learn about workflow APIs in [Workflow endpoints](../rest-api/endpoints/rest-iga.html#rest-api-workflow).