# getFlows

Source: [https://docs.qualcomm.com/doc/80-PK177-134/topic/get_flow.html](https://docs.qualcomm.com/doc/80-PK177-134/topic/get_flow.html)

Retrieves all the flows added by the client along with each associated status.

    getFlows()Copy to clipboard

Note: No callback will be called if the filter stack is empty.

## Parameters

| Parameters | API type | Data type | Description |
| --- | --- | --- | --- |
| cb | Java | IflowStatus | Callback providing the flow information ([iFlowStatus](https://docs.qualcomm.com/doc/80-PK177-134/topic/i_flow_status.html)). Each flow will be a unique API<br>                                call in the callback because vector support is not present in QESDK<br>                                yet. |
| cb | Native | dpp\_flowStatus | Callback providing the flow information ([iFlowStatus](https://docs.qualcomm.com/doc/80-PK177-134/topic/i_flow_status.html)). Each flow will be a unique API<br>                                call in the callback because vector support is not present in QESDK<br>                                yet. |
| ret | Native | int8\_t& | On success this is the actual return value from the API.<br><br><br>                                <br><ul class="ul"><br>                                        <li class="li">1: Success</li><br><br>                                        <li class="li">-1: Iqesdk is null</li><br><br>                                        <li class="li">-2: Subsystem error</li><br><br>                                    </ul> |
|  |  |  |  |

## Returns

| Return | API type | Data type | Description |
| --- | --- | --- | --- |
| response | Java | int | <ul class="ul" id="concept.dita_92bb873b-9de3-48fa-93ec-fa9882e48cf4__ul_tby_fdt_n5b"><br>                                    <li class="li">1: Success</li><br><br>                                    <li class="li">-1: Iqesdk is null</li><br><br>                                    <li class="li">-2: Subsystem error</li><br><br>                                </ul> |
| response | Native | qesdk\_transaction\_status | See [QESDK transaction status for Native APIs](https://docs.qualcomm.com/doc/80-PK177-134/topic/native_qesdk_class.html) for usage details. Use qesdk\_transaction\_status to confirm API call invocation. If successful, use the `ret` value for the actual API return value object. |
|  |  |  |  |

**Parent Topic:** [DPP subsystem APIs](https://docs.qualcomm.com/doc/80-PK177-134/topic/functions.html)

Last Published: Nov 14, 2024

[Previous Topic
addFlow](https://docs.qualcomm.com/bundle/publicresource/80-PK177-134/topics/add_flow.md) [Next Topic
deleteFlow](https://docs.qualcomm.com/bundle/publicresource/80-PK177-134/topics/delete_flow.md)