---
title: "Prism Location Resolutions"
method: POST
path: "/v2/prisms/location-resolutions"
tags: ["Prisms Internal"]
---

# Prism Location Resolutions

`POST /v2/prisms/location-resolutions`

Available location grains for an insight + entity set, as the Prism
service account would see them (same access rules as refresh).

The grains returned are exactly those ``get_framework_filters`` reports for
daily grain — no fabricated fallback. An insight can advertise ``day``
support in the ontology yet have no daily table for a given entity/location
slice, so surfacing a grain that doesn't exist only dead-ends later at
purchase with "no tables found". When nothing is available, ``options`` is
empty and ``default`` is null; CAMS blocks the save rather than offering a
grain that can't be computed.

## Request body

- BodyPrismLocationResolutionsV2PrismsLocationResolutionsPost
  - `payload` PrismLocationResolutionsRequest, required — Insight + entities used to discover available location grains.
    - `insight_id` integer, required
    - `insight_label` string, required
    - `entities` PrismEntityRef[], required
      - `entity_id` integer, required — Carc entity id (representation-scoped)
      - `entity_representation` string, required
      - `entity_name` string, required
  - `config` object, nullable

## Response `200`

Successful Response

- PrismLocationResolutionsResponse
  - `options` PrismLocationOption[], required
    - `value` string, required
    - `label` string, required
  - `default` string, nullable

## 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/revisions/bd33ea42994c/schema)