I am creating a Vapi campaign with more than 1,500 leads. The campaign is successfully created and visible in the Vapi dashboard, however my backend does not receive a response from the Vapi API ( the api timeout ) Because the API response never returns, I am unable to capture and store the campaign ID in my database I have already attempted the following solutions: Queue-based processing Retry mechanisms Caching (Redis) Reconciliation logic Despite these efforts, the issue persists: the campaign exists in Vapi, but my backend has no way to retrieve the campaign ID, since the creation request never completes This makes it impossible to sync or manage the campaign from my backend once it is created

Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team

Since the campaign is created but the API response times out, you can fetch the most recent campaign using the "List Campaigns" endpoint as a workaround. For example, after your create request, call:

bash
curl -X GET "https://api.vapi.ai/campaign?sortOrder=desc&limit=1" \
  -H "Authorization: Bearer <your_token>"

This will return the latest campaign, allowing you to capture the campaign ID for syncing in your backend. For more details, see the [Vapi API documentation](https://docs.vapi.ai/api-reference/campaigns/campaign-controller-find-all?explorer=true). Source: - [Vapi API Reference: List Campaigns](https://docs.vapi.ai/api-reference/campaigns/campaign-controller-find-all?explorer=true)

Hi Ziad, Use the List Campaigns API immediately after your create call to find the campaign when the create request times out. Recommended approach: 1. Send create request. 2. If create times out, call: curl -X GET "https://api.vapi.ai/campaign?sortOrder=desc&limit=1" -H "Authorization: Bearer <your_token>" 3. Match the returned latest campaign by unique fields you sent (name, createdAt window, orgId) to reliably identify the just-created campaign and capture its id. Notes and tips: - To reduce ambiguity when matching, include a unique timestamp or nonce in the campaign name on create. - For very large uploads (1,500+), split recipients into smaller batches (e.g., 50–200) to avoid timeouts/504s during creation (see outbound campaigns overview: https://docs.vapi.ai/outbound-campaigns/overview). - If you see duplicate campaigns from retries, deduplicate by that unique nonce in your DB.

m experiencing a high rate of calls made to the Create Call API and occasionally I receive “Too Many Requests” responses Is there a specific rate limit time window, or recommended delay between requests that I should follow to avoid this issue?