Looking for some advice on troubleshooting this 400 error when creating scorecards via API. We are migrating from Zendesk’s round-robin to Genesys Cloud predictive routing. The payload looks correct based on docs, but it fails.
{
"name": "Zendesk_Ticket_Priority",
"description": "Mapping ZD priority",
"scorecard": [
{
"name": "priority",
"type": "INTEGER",
"weight": 1
}
]
}
Is the structure different?
Check your payload structure against the Genesys Cloud documentation for predictive routing scorecards. The array key used in the request is incorrect. The API expects the attributes to be defined within an attributes array, not a scorecard array. This mismatch causes the server to reject the request with a 400 Bad Request error.
POST /api/v2/predictiverouting/scorecards
400 Bad Request: Invalid JSON payload. Key ‘scorecard’ not found. Expected ‘attributes’.
Adjust the configuration to match the required schema. This ensures the platform can correctly parse the integer weights and types for the Zendesk priority mapping.
{
"name": "Zendesk_Ticket_Priority",
"description": "Mapping ZD priority",
"attributes": [
{
"name": "priority",
"type": "INTEGER",
"weight": 1
}
]
}
This correction aligns with the standard performance views logic. The dashboard will then reflect the correct routing decisions based on the updated scorecard.