---
title: "Get a report on participants added to flow"
method: GET
path: "/moments/1/flows/{campaignId}/participants/report"
tags: ["customer-engagement", "moments", "flow"]
---

# Get a report on participants added to flow

`GET /moments/1/flows/{campaignId}/participants/report`

## Request

- Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infobip.com/moments/1/flows/{campaignId}/participants/report`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `https://api.infobip.com/auth/1/oauth2/token`
  - API key in header `Authorization`
  - API key in header `Authorization`
  - HTTP basic

Use this API endpoint to fetch a report to confirm that all persons have been successfully added to the flow.
                Please note that report is stored for 30 days.

## Path parameters

- `campaignId` integer, required

## Query parameters

- `operationId` string, required
- `applicationId` string
- `entityId` string

## Response `200`

OK

- 900634339512041dd9c6cd5c4ad62d6cf43ea57e0548f5deeceb9f79d92b92f0FlowParticipantsReportResponse: Summary of processing status for participants in a given operation.
  - `operationId` string, required: Unique identifier of the operation.
  - `campaignId` integer, required: Unique identifier of the flow campaign.
  - `callbackData` string, nullable: Additional data will be passed in the request to your callback server along with the operation results report.
  - `participants` 900634339512041dd9c6cd5c4ad62d6cf43ea57e0548f5deeceb9f79d92b92f0AddFlowParticipantResult[], required: Array with information about each participant submitted for the operation.
    - `identifyBy` 900634339512041dd9c6cd5c4ad62d6cf43ea57e0548f5deeceb9f79d92b92f0WebhookPersonUniqueField, required: Unique identifier of the participant.
      - `identifier` string, required: Unique ID for a person
      - `type` 'EMAIL' | 'PHONE' | 'FACEBOOK' | 'LINE' | 'APPLE_BUSINESS_CHAT' | 'EXTERNAL_ID' | 'WHATSAPP', required: Type of unique ID
      - `sender` string, nullable: Sender or application ID.`sender` is required for all identifier types except `PHONE`, `EMAIL`, `EXTERNAL_ID`
    - `status` 'PENDING' | 'REJECTED' | 'ACCEPTED', required: Processing status of the participant.
    - `errorReason` 'REJECTED_INVALID_CONTACT' | 'REJECTED_ATTRIBUTE_MISSED' | 'REJECTED_PERSON_IN_FLOW' | 'REJECTED_PERSON_NOT_ALLOWED_TO_REENTER' | 'REJECTED_FLOW_ERROR_UNKNOWN' | 'REJECTED_NOT_ENOUGH_CREDITS' | 'REJECTED_CDP_ERROR_UNKNOWN': Detailed reason for the REJECTED status: * `REJECTED_INVALID_CONTACT` - Person started to be processed but has been rejected as the contact is not recognized. * `REJECTED_ATTRIBUTE_MISSED` - One of the person's attributes specified in the request does not exist or has spelling error. * `REJECTED_PERSON_ALREADY_IN_FLOW` - Person is already in flow. * `REJECTED_PERSON_NOT_ALLOWED_TO_REENTER` - Person is not allowed to re-enter flow now. * `REJECTED_FLOW_ERROR_UNKNOWN` - Generic flow error. * `REJECTED_NOT_ENOUGH_CREDITS` - Your account is out of credits for further submission. Top up your account. For further assistance in topping up or applying for an online account top-up service, you may contact your Account Manager.

## Other responses

- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `429`: Too Many Requests
- `500`: Internal Server Error

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)