# Workflow Block Instance Processing

**Submitting Block Types in Workflow Instances**\
Workflow Block instances are the operational units of the DOVU OS Workflow Engine. Within each block instance, block types define specific stages or actions, such as data submission, validation, or approval processes. This section focuses on two primary block types:

1. **Data Process Blocks**:\
   These blocks allow users to submit and store structured data related to the workflow. Typical use cases include collecting user information, project details, MRV data, or geographic data necessary for the workflow's progression.
2. **Approval Process Blocks**:\
   These blocks facilitate decision-making steps in the workflow. Users can submit approvals or rejections, with optional messages explaining the decision. This ensures compliance and transparency in workflows requiring oversight or multiple stakeholders.

**How It Works**

* Each block is tied to a specific **workflow instance ID** and acts as a modular step in the broader workflow lifecycle.
* Each block is tied to a specific role that can act on the block, all roles are connected actors that must be prior connected to a workflow instance from the owner or registry actor.
* Developers can interact with these blocks via POST requests, submitting data that drives the instance forward or changes its state.
* Responses from these endpoints include metadata about the workflow instance, enabling further actions or integrations.

**Key Use Cases**:

* Submitting project data for environmental credit issuance.
* Approving or rejecting specific workflow stages to ensure compliance.
* Using returned data for visualization or tracking in front-end applications.

With these endpoints, developers can manage workflow instances dynamically, ensuring seamless integration of data submissions and approvals into the workflow lifecycle.

***

{% openapi src="/files/8Pvw8mj5JRwQoHlDDzln" path="/api/v1/workflow-block-instances/data\_workflow\_block\_instance\_id" method="post" %}
[DOVU OS.openapi(2).yaml](https://116257023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMgfYR4iNMhdWqFrJ1ibn%2Fuploads%2F06V2ZUViujbBzewa1wXh%2FDOVU%20OS.openapi\(2\).yaml?alt=media\&token=ba5bcc29-0fb4-48cf-9884-1823433ae77d)
{% endopenapi %}

{% openapi src="/files/8Pvw8mj5JRwQoHlDDzln" path="/api/v1/workflow-block-instances/approval\_workflow\_block\_instance\_id" method="post" %}
[DOVU OS.openapi(2).yaml](https://116257023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMgfYR4iNMhdWqFrJ1ibn%2Fuploads%2F06V2ZUViujbBzewa1wXh%2FDOVU%20OS.openapi\(2\).yaml?alt=media\&token=ba5bcc29-0fb4-48cf-9884-1823433ae77d)
{% endopenapi %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dovu.earth/workflow-engine/editor/workflow-block-instance-processing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.