---
title: "Retrieve bulk wallet operation status"
method: GET
path: "/v2/wallets/bulk/status/{id}"
tags: ["BulkWalletOperations"]
---

# Retrieve bulk wallet operation status

`GET /v2/wallets/bulk/status/{id}`

This endpoint retrieves the status of a bulk wallet operation using its bulk ID. It has been enhanced to support pagination (default: 20 items per page) and status-based filtering, for improved performance and targeted data retrieval. Use this endpoint to check the progress and completion status of bulk update operations.

## Path parameters

- `id` string, required

## Query parameters

- `pageToken` string
- `pageSize` string, int64
- `status` string

## Response `200`

Details of the bulk operation status and progress.

- V2BulkWalletStatusResponse
  - `bulkId` string — Unique identifier for the bulk operation.
  - `resource` 'BULK_OPERATION_RESOURCE_BILLING' | 'BULK_OPERATION_RESOURCE_CAMPAIGN' | 'BULK_OPERATION_RESOURCE_AUTH'
  - `operationType` 'BULK_OPERATION_TYPE_CAMPAIGN_UPDATE' | 'BULK_OPERATION_TYPE_CAMPAIGN_STATE_UPDATE' | 'BULK_OPERATION_TYPE_WALLET_UPDATE' | 'BULK_OPERATION_TYPE_TEAM_UPDATE' | 'BULK_OPERATION_TYPE_WALLET_CREATE' | 'BULK_OPERATION_TYPE_TEAM_CREATE' | 'BULK_OPERATION_TYPE_CAMPAIGN_CREATE' | 'BULK_OPERATION_TYPE_INVITE_USER' | 'BULK_OPERATION_TYPE_REMOVE_USER'
  - `status` 'BULK_OPERATION_SUBMITTED' | 'BULK_OPERATION_IN_PROGRESS' | 'BULK_OPERATION_COMPLETED' | 'BULK_OPERATION_FAILED'
  - `totalCount` string, int64 — Total number of items in the bulk operation.
  - `successCount` string, int64 — Number of items processed successfully.
  - `failureCount` string, int64 — Number of items that failed processing.
  - `createdAt` string, date-time — Timestamp when the bulk operation was created.
  - `updatedAt` string, date-time — Timestamp when the bulk operation was last updated.
  - `items` Citrusbillingv2BulkOperationItem[]
    - `status` 'BULK_ITEM_SUCCESS' | 'BULK_ITEM_FAILED'
    - `successResponse` Citrusbillingv2SuccessResponse
      - `message` string — Success message for the operation.
      - `walletId` string — The unique identifier of the wallet that was processed.
    - `errorResponse` V1ErrorResponse
      - `details` string — Error details describing what went wrong during the operation.
    - `updateWalletRequest` Billingv2UpdateWallet
      - `id` string, required — The wallet identifier.
      - `namespaceId` string — The namespace identifier that associates the wallet with a team.
      - `teamId` string — The unique team identifier assigned for the wallet.
      - `name` string — The wallet name.
      - `externalId` string — The optional external ID field for storing custom identifiers such as Placement IO numbers, purchase order numbers, or Salesforce numbers for tracking purposes. Partners can use this field to associate external identifiers with the wallet. Must be shorter than 255 characters.
      - `currencyCode` string — The wallet currency code using the 3-letter ISO 4217 standard.
      - `creditLimit` string — The maximum credit limit for the wallet.
      - `dailyBudget` string — The daily spending limit for the wallet.
      - `archived` boolean — Whether the wallet is archived.
    - `createWalletRequest` V2Wallet
      - `id` string — The wallet identifier.
      - `namespaceId` string, required — The namespace identifier that associates the wallet with a team.
      - `teamId` string, required — The unique team identifier assigned for the wallet.
      - `name` string, required — The wallet name.
      - `externalId` string — The optional external ID field for storing custom identifiers such as Placement IO numbers, purchase order numbers, or Salesforce numbers for tracking purposes. Partners can use this field to associate external identifiers with the wallet. Must be shorter than 255 characters.
      - `currencyCode` string, required — The wallet currency code using the 3-letter ISO 4217 standard.
      - `dailyBudget` string — The daily spending limit for the wallet.
  - `nextPageToken` string — Token to retrieve the next page of results.

## Other responses

- `400` — There was a problem with input.
- `401` — Login failed or token not valid.
- `403` — Access denied due to insufficient permissions.
- `default` — An unexpected error response.

---

[API](https://skmtc.net/citrusad/apis/citrus-auth-api.md) · [All operations](https://skmtc.net/citrusad/apis/citrus-auth-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/citrusad/citrus-auth-api/revisions/a040003c7378/schema)