An unexpected field is included in the API response, which is not documented in the API specification. This discrepancy could cause issues in client implementations and automated tests that rely on the API spec.
Steps to Reproduce:
Send a request to the affected API endpoint.
Observe the response received.
Identify the presence of the undocumented field in the JSON response.
Expected Result:
The API response should match the documented schema. All fields returned should be defined in the API specification.
Actual Result:
The response includes an undocumented field, leading to potential discrepancies.
Evidence:
Response Screenshot: See attached screenshot showing the unexpected field highlighted (e.g., visibilityType).
API Specification Screenshot: Shows the field is not listed in the official documentation.
Also adding the spec valid for 30 mins.
Please visit the following link to obtain the API specification for the endpoint “Get rewards for the app”: https://api.apidog.com/temp-links/api/22363203?t=021c07b6-5d80-4e2f-9e7a-4ed09e5ccb65
Priority: Medium
Severity: High
Additional Notes:
This issue may lead to misunderstandings or errors in consuming the API, as clients and tests expect the response to strictly follow the defined schema.
Example:
While using the “Get rewards for the app” endpoint, a field visibilityType was returned in the response but was not present in the API spec.
