---
title: "Retrieve profiles from your workspace v2"
method: GET
path: "/v2/query/clients"
tags: ["Query"]
---

# Retrieve profiles from your workspace v2

`GET /v2/query/clients`

Retrieve workflows user submissions. This is different from events because it contains the whole data submitted by a user.The parameters `before` and `after` can be passed to define a time range for your search

## Query parameters

- `before` string — Filters for results based on their creation date. Returns clients created before the specified UNIX timestamp.
- `after` string — Filters for results based on their creation date. Returns clients created after the specified UNIX timestamp.
- `last-modified-before` string — Filters for results based on their last-modified date. Returns clients last modified before the specified UNIX timestamp.
- `last-modified-after` string — Filters for results based on their last-modified date. Returns clients last modified after the specified UNIX timestamp.
- `limit` string — Maximum number of items to be returned. Must be between 1 - 50 both inclusive. Omitting the limit parameter or using an invalid value will default to 20.
- `page` string — You can specify further pages with this parameter. Page numbering is 0-based and omitting the page parameter or using an invalid value will return the first page.
- `statuses` string — You can specify the desired end client statuses to filter the results with. Omitting the statuses parameter will return end clients for all available statuses
- `flowId` string — You can specify the desired flow id to filter the results with. Only end clients that have interacted with that flow will be returned.

## Response `200`

OK

- ExportPageProfileDataResourceSummary
  - `totalElements` integer
  - `totalPages` integer
  - `number` integer
  - `numberOfElements` integer
  - `last` boolean
  - `first` boolean
  - `data` ProfileDataResourceSummary[]
    - `id` string — Unique identifier that coincides with the user
    - `ownerIds` string[] — The IDs of the owners of the user that interacted with the workflow
    - `created` integer — Date that indicates the first interaction of the user with the workflow
    - `lastModified` integer — Date that indicates the last interaction of the user with the workflow
    - `profileType` 'NORMAL' | 'OWNER' — Indicates if the profile is corporate/individual
    - `status` 'ACCEPTED' | 'REJECTED' | 'IN_PROGRESS' | 'PENDING_REVIEW' | 'NOT_STARTED' | 'ABANDONED' — End client status. When an end client completes the flow without encountering an "Accept" or "Reject" node, they are considered to be in a pending review state. This occurs when the flow does not explicitly provide a status decision at the end.
    - `statusManuallyChanged` boolean — Indicates whether there has been a manual status update at some point in the profile's history. It is important to note that this does not necessarily mean the current status of the profile was manually updated.
    - `user` string — The user ID belonging to the user that interacted with the workflow

---

[API](https://skmtc.net/trulioo/apis/trulioo-platform-api.md) · [All operations](https://skmtc.net/trulioo/apis/trulioo-platform-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/trulioo/trulioo-platform-api/versions/a825565ee177/schema)