- The /v1/partner_risks API is functioning as designed. The reason you're only seeing three columns at the top level is due to how the API response is structured. Here's a detailed explanation:
- Top-Level Attributes in /v1/partner_risks API
- The API response includes the following top-level fields as id, external_ids and risks.
- These are the only fields that will appear directly as independent columns when parsing the raw API response.
- The fields such as: "Risk component name" and "risk_type" are not top-level attributes. Instead, they are nested within the risks array, which is a JSON structure inside each record.
- Therefore, they won’t appear as independent columns or attributes in the primary response schema.
- Please refer to the screenshot below for an example of how the data is structured in the response of partner_risks API endpoint:
- As such, these nested fields cannot be queried or filtered directly, but you can extract them by parsing through the risks array.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article