Bulk Delete Prospects
Prospects
Bulk Delete Prospects
Delete multiple prospects in a single operation
DELETE
Bulk Delete Prospects
Documentation Index
Fetch the complete documentation index at: https://docs.kakiyo.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Delete multiple prospects in a single operation. This endpoint efficiently processes bulk deletions with detailed results for each prospect. Maximum 100 prospects per request. This action cannot be undone.Request Body
Array of prospect IDs to delete (maximum 100)
Optional campaign ID to filter prospects (additional safety check)
Use Cases
- Campaign Cleanup: Remove multiple invalid prospects
- Data Migration: Clean up prospects during system migrations
- Compliance: Bulk removal for GDPR/privacy requests
- Quality Control: Remove prospects that don’t meet updated criteria
Important Considerations
Request Example
Response Structure
Testing Example
Error Responses
Invalid Request
Too Many Prospects
Campaign Mismatch
Batch Processing Strategy
For large-scale deletions, implement batch processing:Result Analysis
Analyze bulk deletion results:Best Practices
- Batch Size: Use 25-50 prospects per batch for optimal performance
- Error Handling: Always check individual results for failures
- Rate Limiting: Add delays between large batch operations
- Data Backup: Export data before bulk deletions
- Progress Tracking: Implement progress indicators for large operations
Safety Measures
Campaign Filtering
UsecampaignId parameter as an additional safety check:
Validation Steps
- Verify prospect ownership before deletion
- Check for active conversations
- Confirm campaign association if specified
- Validate prospect existence
Recovery Considerations
No Recovery Available: Bulk deleted prospects cannot be recovered. For large operations:
- Test with small batches first
- Keep detailed logs of deletions
- Export critical data before deletion
- Consider implementing soft deletes in your application
Performance Optimization
For optimal performance:- Use appropriate batch sizes (25-50 prospects)
- Process during off-peak hours
- Monitor API rate limits
- Implement exponential backoff for retries
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
application/json
Prospect IDs to delete
Last modified on January 28, 2026

