---
title: "Get accounting intelligence settings"
method: GET
path: "/v2/accounting/intelligence"
---

# Get accounting intelligence settings

`GET /v2/accounting/intelligence`

## Request

- Base URL: `https://api.slash.com`
- URL: `https://api.slash.com/v2/accounting/intelligence`
- Auth: API key in header `X-API-Key`

Get which dimensions the accounting intelligence agent codes automatically.

## Query parameters

- `connectionId` string

## Response `200`

The connection's intelligence settings.

- AccountingIntelligenceSettings: How the accounting intelligence agent auto-codes a connection's entries. The agent reads a transaction's merchant, card and history, proposes a value for each enabled dimension and writes it as an `ai` mapping, so its work shows up in `GET /v2/accounting/mappings` and can be corrected there.
  - `connectionId` string, required
  - `mode` 'disabled' | 'all_fields' | 'selected_fields', required: `disabled` never auto-codes. `all_fields` auto-codes every dimension in `supportedDimensionKeys`. `selected_fields` auto-codes only the dimensions chosen in `enabledDimensionKeys`.
  - `enabledDimensionKeys` string[], required: The dimensions the agent codes under the current mode: empty when `disabled`, every supported key when `all_fields`, the chosen keys when `selected_fields`.
  - `supportedDimensionKeys` string[], required: The dimensions the agent can code on this platform.

## Other responses

- `400`: - `connection_id_required` — The legal entity has several accounting connections, so the request must say which one with `connectionId`. List them with `GET /v2/accounting/connections`. - `invalid_request (request shape)` — The body, query, or headers failed validation, or a required header is missing. `details` has one entry per failing location, keyed by JSON pointer or header name.
- `401`: - `unauthorized` — API key authentication is missing or invalid.
- `403`: - `forbidden (legal entity)` — The credential is not permitted to act for the selected legal entity. - `not_available` — Public API v2 is not yet available. Use [Public API v1](https://docs.slash.com/introduction) in the meantime. - `user_api_key_required` — The API key is scoped to a legal entity rather than a user. Every v2 request needs a user API key, created under Settings → API keys in the Slash dashboard, together with the `x-legal-entity` header.
- `404`: - `not_found` — No resource matches the identifier. When the identifier is a field of the request, `details` names that `field` and the `id` it received.
- `429`: The request exceeded the applicable rate limit. The response body is plain text, not the error object; clients must not depend on its wording.
- `500`: - `internal` — Slash could not complete the request. Quote `referenceId` when contacting Slash support.

## Changes

- **2026-10-16** `8b5d371ffeea`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/slashfi/apis/slash-public-api/changes/v2/accounting/intelligence/get.md)

---

[API](https://skmtc.dev/slashfi/apis/slash-public-api.md) - [All operations](https://skmtc.dev/slashfi/apis/slash-public-api/llms.txt) - [OpenAPI document](https://skmtc.dev/slashfi/apis/slash-public-api/revisions/eaed2d63c9e2?raw)