---
title: "Linked Insight Ids"
method: GET
path: "/v2/ontology/insights/linked"
tags: ["Ontology"]
---

# Linked Insight Ids

`GET /v2/ontology/insights/linked`

Insight ids linked to the requested entity / event scope.

The browser already holds the whole catalog from ``/all-insights``,
so scoping a browse only needs graph adjacency: it intersects these ids
with the corpus it has instead of refetching a listing. Adjacency is not
user-specific — provider access is already applied to the catalog the ids
are intersected with.

Scopes AND together, the same way the paginated listing stacks its entity
and event pre-filters. Adjacency does not vary with subject/topic/dataset
filters, so those are not accepted here — the caller narrows the
intersection it already holds.

## Query parameters

- `entity_id` integer[], nullable — Entity carc_ids (paired with entity_representation)
- `entity_representation` string[], nullable — Representations paired 1:1 with entity_id
- `event_id` integer, nullable — carc_id of an event EntityRepresentation (paired with event_representation).
- `event_representation` string, nullable — Representation type of the event node (e.g. 'corpeventc').
- `event_category_id` integer, nullable — carc_id of an EventCategory — insights linked to any event under it.

## Request body

- object, nullable

## Response `200`

Successful Response

- InsightLinkedResponse — Insight ids linked to the requested entity / event scope. Adjacency only — the client already holds the catalog and intersects locally, so scoping a browse costs an id list, not a listing.
  - `insight_ids` integer[], required

## Other responses

- `404` — Not Found
- `422` — Validation Error

---

[API](https://skmtc.net/carbonarc/apis/carbon-arc-api-documentation.md) · [All operations](https://skmtc.net/carbonarc/apis/carbon-arc-api-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/carbonarc/carbon-arc-api-documentation/versions/bd33ea42994c/schema)