Stuck on mapping the Zendesk Satisfaction Survey to the Genesys Cloud Interaction Analytics API. The GET /api/v2/analytics/interactions/query endpoint throws a 400 Bad Request with invalid_field: satisfaction_score. In Zendesk, this was a simple custom field, but GC seems to require a specific survey integration setup. How do I correctly reference the satisfaction metric in the query payload for migrated interactions?
The official documentation states that satisfaction_score isn’t a valid field for the interactions query endpoint, which explains the 400 error. When migrating from Zendesk, those custom fields don’t automatically map to Genesys Cloud’s standard survey metrics. You need to check if the survey integration is fully configured and look for the specific metric name in the metrics object of the interaction data, usually something like survey.satisfaction_rating. For load testing this, I usually spin up a quick JMeter test to verify the field exists before scaling up. Here is a basic payload structure to check: {"query": "type:interaction", "metrics": ["survey.satisfaction_rating"]}. If that still fails, double-check the survey template ID in the admin console. It’s easy to miss a configuration step during migration, especially when dealing with high concurrency later. The API is strict about field names, so guessing won’t work. Try listing the available metrics first using the analytics schema endpoint. This usually saves a lot of trial and error.
Generally speaking, the standard survey metrics are distinct from custom attributes in the query schema. Verify the exact field path in the documentation here: https://developer.genesys.cloud/api/v2/analytics/interactions/query.