--- title: Get response feedback url: https://developers.wpengine.com/docs/ai/api/reference/operations/getresponsefeedback/ image: https://developers.wpengine.com/og/docs/ai/api/reference/operations/getresponsefeedback.png --- # Get response feedback GET /v1/sessions/{session_id}/responses/{response_event_id}/feedback Select code sample ```php request('GET', 'https://api.ai.wpengine.com/v1/sessions/example/responses/example/feedback', [ 'headers' => [ 'Authorization' => 'Bearer ', ], ]); echo $response->getBody(); ``` - Current environment Returns the feedback recorded for a single agent response. Responds with 404 when the response has not been rated, which is the normal case for most responses — treat it as “no rating yet” rather than an error. Accepts a service-token bearer authenticating a site or an API key, either of which must be authorized for the session’s project, or a browser session token holding the session_events scope (bound to the session’s agent and, when the session records an owner_id, to that same visitor). ## Authorizations - **[bearerAuth](https://developers.wpengine.com/docs/ai/api/reference/#bearerauth)** ## Parameters ### Path Parameters **session_id** required string The session ID. **response_event_id** required string The id of the agent.message event being rated, as returned by GET /v1/sessions/{session_id}/events. ## Responses ### 200 The feedback recorded for this response Media typeapplication/json object **response_event_id** required The agent.message event this feedback is about. string **rating** required True for a thumbs-up, false for a thumbs-down. boolean **message** The comment as stored, or null when none was given. Always present so “rated without a comment” is unambiguous. string nullable **created_at** required When the feedback was recorded. string format: date-time #### Example generated ```json { "response_event_id": "example", "rating": true, "message": "example", "created_at": "2026-04-15T12:00:00Z" } ``` ### 400 Invalid request body or parameters. On agent create and update, error type “profile_unavailable” means the requested profile is not available to the caller. Media typeapplication/json object **error** required object **message** required string **type** required string **error_code** Stable, machine-readable cause, set by routes that document their codes (the AI readiness and account AI routes, and an entitlement_required refusal, where it is one of not_eligible, terms_required, not_enabled or suspended); absent elsewhere and on errors from shared layers such as authentication. Clients must allow new codes. string **portal_url** Where the customer can resolve the error, set on an entitlement_required refusal that has an error_code when one is configured. string **code** required integer **request_id** required Correlation ID for this request, matching the X-Request-ID response header — a 32-character trace ID behind the load balancer, otherwise a UUID. Quote it in support reports. string #### Example ```json { "error": { "type": "invalid_request_error", "request_id": "80f1e2c3a4b5c6d7e8f9a0b1c2d3e4f5" } } ``` ### 401 Missing or invalid bearer token Media typeapplication/json object **error** required object **message** required string **type** required string **error_code** Stable, machine-readable cause, set by routes that document their codes (the AI readiness and account AI routes, and an entitlement_required refusal, where it is one of not_eligible, terms_required, not_enabled or suspended); absent elsewhere and on errors from shared layers such as authentication. Clients must allow new codes. string **portal_url** Where the customer can resolve the error, set on an entitlement_required refusal that has an error_code when one is configured. string **code** required integer **request_id** required Correlation ID for this request, matching the X-Request-ID response header — a 32-character trace ID behind the load balancer, otherwise a UUID. Quote it in support reports. string #### Example ```json { "error": { "type": "invalid_request_error", "request_id": "80f1e2c3a4b5c6d7e8f9a0b1c2d3e4f5" } } ``` #### Headers **WWW-Authenticate** string ##### Example ``` Bearer realm="ai-services" ``` ### 403 The token is valid, but the request is forbidden. Error type “permission_error” means the token’s scope/permission is insufficient or the authenticated user is not authorized for the target account; “entitlement_required” means the account may not use WP Engine AI, with error_code giving why when known (not_eligible, terms_required, not_enabled or suspended) and portal_url where to fix it; “account_required” means no billing account could be resolved; and “billing_account_pending” means billing isn’t set up for the account yet, usually because its setup after AI was turned on hasn’t finished. Retry shortly. On /v1/chat/completions when content moderation is enabled, and on /v1/sessions/{session_id}/events, error type “content_policy_violation” instead means the request content was blocked by content moderation policy; that response never identifies which filter or category matched. Media typeapplication/json object **error** required object **message** required string **type** required string **error_code** Stable, machine-readable cause, set by routes that document their codes (the AI readiness and account AI routes, and an entitlement_required refusal, where it is one of not_eligible, terms_required, not_enabled or suspended); absent elsewhere and on errors from shared layers such as authentication. Clients must allow new codes. string **portal_url** Where the customer can resolve the error, set on an entitlement_required refusal that has an error_code when one is configured. string **code** required integer **request_id** required Correlation ID for this request, matching the X-Request-ID response header — a 32-character trace ID behind the load balancer, otherwise a UUID. Quote it in support reports. string #### Example ```json { "error": { "type": "invalid_request_error", "request_id": "80f1e2c3a4b5c6d7e8f9a0b1c2d3e4f5" } } ``` ### 404 The requested resource was not found Media typeapplication/json object **error** required object **message** required string **type** required string **error_code** Stable, machine-readable cause, set by routes that document their codes (the AI readiness and account AI routes, and an entitlement_required refusal, where it is one of not_eligible, terms_required, not_enabled or suspended); absent elsewhere and on errors from shared layers such as authentication. Clients must allow new codes. string **portal_url** Where the customer can resolve the error, set on an entitlement_required refusal that has an error_code when one is configured. string **code** required integer **request_id** required Correlation ID for this request, matching the X-Request-ID response header — a 32-character trace ID behind the load balancer, otherwise a UUID. Quote it in support reports. string #### Example ```json { "error": { "type": "invalid_request_error", "request_id": "80f1e2c3a4b5c6d7e8f9a0b1c2d3e4f5" } } ``` ### 429 Rate limit exceeded. The request was throttled at the edge; wait and retry later. The response body is a short HTML page generated by the load balancer, not a structured JSON error — clients should rely on the 429 status code rather than parsing the body. Media typetext/html string ### 500 The server encountered an unexpected error while handling the request. Safe to retry once; if it persists, the cause is server-side and the request payload was not the problem. Media typeapplication/json object **error** required object **message** required string **type** required string **error_code** Stable, machine-readable cause, set by routes that document their codes (the AI readiness and account AI routes, and an entitlement_required refusal, where it is one of not_eligible, terms_required, not_enabled or suspended); absent elsewhere and on errors from shared layers such as authentication. Clients must allow new codes. string **portal_url** Where the customer can resolve the error, set on an entitlement_required refusal that has an error_code when one is configured. string **code** required integer **request_id** required Correlation ID for this request, matching the X-Request-ID response header — a 32-character trace ID behind the load balancer, otherwise a UUID. Quote it in support reports. string #### Example ```json { "error": { "type": "invalid_request_error", "request_id": "80f1e2c3a4b5c6d7e8f9a0b1c2d3e4f5" } } ``` ### 503 A required dependency is temporarily unavailable. Retry after a short delay with exponential back-off. An entitlement lookup failure uses error type “entitlement_unavailable”. A model without complete rate coverage uses error type “model_unpriced”. A credit balance that can’t be read uses error type “balance_unavailable”. Media typeapplication/json object **error** required object **message** required string **type** required string **error_code** Stable, machine-readable cause, set by routes that document their codes (the AI readiness and account AI routes, and an entitlement_required refusal, where it is one of not_eligible, terms_required, not_enabled or suspended); absent elsewhere and on errors from shared layers such as authentication. Clients must allow new codes. string **portal_url** Where the customer can resolve the error, set on an entitlement_required refusal that has an error_code when one is configured. string **code** required integer **request_id** required Correlation ID for this request, matching the X-Request-ID response header — a 32-character trace ID behind the load balancer, otherwise a UUID. Quote it in support reports. string #### Example ```json { "error": { "type": "invalid_request_error", "request_id": "80f1e2c3a4b5c6d7e8f9a0b1c2d3e4f5" } } ``` ## Was this helpful? Thanks for the feedback! ```json {"@context":"https://schema.org","@graph":[{"@type":"WebSite","@id":"https://developers.wpengine.com/#website","name":"WP Engine Product Documentation","url":"https://developers.wpengine.com/","description":"Resources for developing, deploying, and scaling on WP Engine.","inLanguage":"en-US","keywords":["API documentation","product documentation","headless WordPress","managed WordPress hosting"],"publisher":{"@id":"https://wpengine.com/#organization"}}]} ```