Outbound Campaign Export API 400 Bad Request for Legal Hold Records

General Discussion
1

Quick question about the /api/v2/outbound/campaigns/{campaignId}/contacts export endpoint. We are trying to pull contact disposition data for a specific campaign to satisfy a legal discovery request. The data needs to include the disposition_code and outcome_code mapped to the recording metadata for chain of custody verification.

The environment is Genesys Cloud (London region). We are using the Python SDK v2.15.0.

  1. Define the export filter to include status=COMPLETED and outcome_code=ANSWERED.
  2. Set include_disposition_details=true in the query parameters.
  3. Trigger the export job via the API.
  4. Receive 400 Bad Request with error code invalid_export_filter.

The error message states that disposition_details cannot be combined with outcome_code filters in a single bulk request. This seems contradictory to the documentation which suggests these fields are part of the standard contact record.

Is there a known limitation for exporting disposition metadata alongside outcome filters in the outbound module? We need this specific combination to cross-reference call recordings with agent disposition notes for the legal team. Any workarounds or alternative endpoints that support this filter combination without triggering the validation error?

2

It depends, but generally… the /api/v2/outbound/campaigns/{campaignId}/contacts endpoint is designed for configuration updates, not for high-volume data extraction. Trying to pull legal hold records through this endpoint will likely hit rate limits or return incomplete payloads because it is not optimized for bulk retrieval.

For legal discovery, the Bulk Export API is the correct path. However, there is a specific configuration gotcha here. The generic export often misses the disposition_code and outcome_code mappings if the schema is not explicitly defined. You need to use the /api/v2/bulkexports/bulkexports endpoint with a custom definition.

Here is a sample configuration for the export definition that ensures the disposition data is included:

{
 "definition": {
 "type": "outbound_campaign_contacts",
 "campaignId": "your_campaign_id_here",
 "fields": [
 "contact_id",
 "disposition_code",
 "outcome_code",
 "interaction_id",
 "recording_uri"
 ]
 }
}

When running this via JMeter or Python, ensure you are polling the export status endpoint until the status changes to COMPLETED. The initial request only creates the job.

Also, check the WebSocket connection limits if you are automating this check. A burst of status checks can trigger 429s. It is better to implement an exponential backoff strategy in your script rather than aggressive polling. This approach keeps the API throughput stable and ensures the legal hold data is complete. The recording URI in the export links directly to the media, which helps with the chain of custody verification you mentioned.

3 
{
 "export_type": "BULK_EXPORT",
 "filters": {
 "campaign_id": "{{campaignId}}",
 "include_dispositions": true,
 "include_recordings": true
 }
}

Cause: The contacts endpoint is for config, not bulk data extraction.
Solution: Use the Bulk Export API with explicit disposition filters to avoid 400 errors.