Successfully retrieved the holdout with all its configuration details.

Response includes:

• Core properties: ID, key, name, description, status, traffic allocation
• Lifecycle data: Created/updated timestamps, start/end times (if applicable)
• Configuration: Environment, audience conditions, metrics setup
• Experiment rules: Associated experiments and their allocation settings
• Management links: URLs for update, archive, delete operations (if authorized)
• System metadata: URN, project association, archive status

Link availability depends on user permissions:

• Missing update_url: Cannot modify this holdout
• Missing delete_url: Cannot permanently delete
• Missing archive_url/unarchive_url: Cannot change archive status

Status-specific data:

• Draft holdouts: Full configuration, no timing data
• Running holdouts: Includes start_time, active experiment rules
• Concluded holdouts: Includes both start_time and end_time

Bad Request - Invalid request parameters or malformed holdout ID.

Common causes:

• Invalid holdout_id format (must be a positive integer)
• Invalid project_id format (must be a positive integer)
• Malformed request structure or unsupported query parameters

Invalid credentials

Do not have permission to perform the operation

Not Found - The specified holdout does not exist or you don't have access to it.

Possible reasons:

• Holdout ID does not exist in the specified project
• Project ID does not exist or you don't have access to it
• Holdout was permanently deleted
• Insufficient permissions to view this holdout