Can anyone clarify the schema requirement for custom dimensions in the reporting export API?
Running GC CLI v2.1.0 against the Sydney region. The standard interaction export works, but adding routing_trunk and agent_skill to the dimensions array triggers a 400 Bad Request. The payload is valid JSON. Error body returns dimension_invalid: unsupported dimension for report type. Using reporting:report:execute scope. Terraform state shows these dimensions exist in the org. Is there a hidden constraint on which dimensions can be combined in a single export request via the API?
This is typically caused by the specific report type not supporting those custom dimensions in the execution payload. The interaction report type often restricts certain routing attributes unless explicitly defined in the schema for that region.
{
"reportType": "routing:interaction:detail",
"interval": "PT1H",
"dimensions": [
"routing_trunk",
"agent_skill"
],
"filter": {
"type": "equals",
"dimension": "routing_trunk",
"value": "trunk-id-123"
}
}
Check the API documentation for routing:interaction:detail specifically. The standard interaction export usually only supports basic metrics. Using the correct report type ID resolves the 400 error. Also verify the scope includes analytics:report:export.