Just noticed that the bulk export job fails immediately with a 422 Unprocessable Entity when including the chain_of_custody_ref field in the request payload.
The API documentation does not explicitly forbid this custom metadata key for legal discovery requests. Is there a schema validation issue in the current version of the Recording API?
The documentation actually says custom metadata fields must be prefixed with custom_ to bypass schema validation. The 422 error indicates the parser rejected the raw key. Try adjusting the payload structure below. This aligns with standard BYOC metadata handling rules.
{
"export_type": "legal_hold",
"metadata": {
"custom_chain_of_custody_ref": "value"
}
}{
“export_type”: “legal_hold”,
“metadata”: {
“custom_chain_of_custody_ref”: “value”
}
}
The prefix resolved the validation error. The 422 response was indeed caused by the schema rejecting the raw key without the required custom_ identifier.