> ## Documentation Index > Fetch the complete documentation index at: https://docs.ringg.ai/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > To search or read these docs, connect the Ringg docs MCP server at https://docs.ringg.ai/mcp (no key needed; tools search_ringg_ai and query_docs_filesystem_ringg_ai) instead of browsing pages one by one. Setup for each client: https://docs.ringg.ai/resources/mcp-server/docs-mcp-server/mcp-for-ai-assistants.md > The dashboard labels agents "Assistants"; these docs say "agent". Both mean the same object, identified by agent_id. > API base URL: https://prod-api.ringg.ai/ca/api/v0. Send the workspace API key in the X-API-KEY header, from server-side code only. > Placing a call dials a real phone number and spends credits. Confirm the number with the user before calling. > To act on a Ringg workspace (place calls, edit agents, read transcripts), use the separate Ringg workspace MCP server at https://mcp.ringg.ai/mcp: https://docs.ringg.ai/resources/mcp-server/workspace-mcp-server/overview.md # Get large campaign upload status (Beta) > Poll the validation status of a large campaign CSV by bulk_list_id until it is draft and ready to start, or fails, has no valid rows or lacks balance. export const RelatedTopics = ({items}) =>
Related topics
{items.map(([title, href]) => {title} )}
; Poll it every few seconds after [Upload large campaign CSV](/api-reference/calling/large-campaigns/upload-large-campaign-csv), until `status` stops changing. ## Statuses | `status` | Meaning | Next | | - | - | - | | `verifying` | Rows are still being validated | Keep polling | | `draft` | The list is valid and ready | [Start calls](/api-reference/calling/large-campaigns/make-large-campaign-calls-async) | | `no_valid_contacts` | Every row was invalid | Fix the CSV and upload it again | | `insufficient_balance` | The workspace balance does not cover the list | Add balance, then [re-check the balance](/api-reference/calling/large-campaigns/check-large-campaign-balance) | | `failed` | Validation could not finish | Upload again | The response also reports `total_callees`, the valid contacts loaded, and `invalidated_rows_count`, the rows that failed validation. After launch, `status` follows the campaign: `preparing`, `in_db`, `scheduled`, `ongoing`, `completed` or `terminated`. ## OpenAPI ````yaml get /campaign/upload-status/{bulk_list_id} openapi: 3.0.0 info: title: Ringg AI API Documentation description: >- The Ringg AI REST API. Base URL https://prod-api.ringg.ai/ca/api/v0; send your workspace API key in the X-API-KEY header from server-side code only. Requests and responses are JSON. version: 2.0.0 contact: name: Ringg AI support email: admin@ringg.ai url: https://docs.ringg.ai servers: - url: https://prod-api.ringg.ai/ca/api/v0 security: [] tags: - name: workspace description: Endpoints for managing your workspace. - name: agent description: Endpoints for managing agents. - name: calling description: Endpoints for making and managing calls. - name: campaign description: Endpoints for managing campaigns. - name: analytics description: Endpoints for accessing call analytics and performance metrics. - name: termination description: Endpoints for terminating active calls using different methods. - name: knowledgebase description: Endpoints for managing knowledge bases. paths: /campaign/upload-status/{bulk_list_id}: get: tags: - campaign summary: Get Campaign Upload Status (Beta) description: >- Beta endpoint for checking asynchronous CSV validation status before starting a large campaign. operationId: getCampaignUploadStatusBeta parameters: - name: X-API-KEY in: header description: (Required) Your Ringg AI API key. required: true schema: type: string example: rg_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx - name: bulk_list_id in: path required: true description: Bulk list ID returned by /campaign/upload-csv. schema: type: string responses: '200': description: Upload status returned successfully. content: application/json: schema: type: object properties: bulk_list_id: type: string example: 123e4567-e89b-12d3-a456-426614174000 status: type: string description: >- `verifying`: still being checked, keep polling. `draft`: valid and ready to start with /campaign/make-call-async. `no_valid_contacts`: every row was invalid. `insufficient_balance`: add balance, then call /campaign/check-balance/{bulk_list_id}. `failed`: processing failed; upload again. After launch the campaign's own status is returned: `preparing`, `in_db`, `scheduled`, `ongoing`, `completed` or `terminated`. enum: - verifying - draft - no_valid_contacts - insufficient_balance - failed - preparing - in_db - scheduled - ongoing - completed - terminated example: draft campaign_name: type: string example: Renewal reminders - large upload total_callees: type: integer description: Valid contacts loaded example: 4988 invalidated_rows_count: type: integer description: Rows dropped as invalid example: 12 '401': description: Unauthorized - Invalid or missing authentication. content: application/json: schema: type: object properties: message: type: string example: Invalid credentials '404': description: Not Found - No campaign with this ID in the workspace. content: application/json: schema: type: object properties: message: type: string example: Campaign not found or you don't have access to it. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.