---
title: "Get Data Processing Settings"
method: GET
path: "/v1/settings/data-processing"
tags: ["Settings", "v1"]
---

# Get Data Processing Settings

`GET /v1/settings/data-processing`

Returns the current "Allow third-party providers" state for the account and its full change history, ordered most-recent-first. Each changelog entry records what was set, who set it, and when.

:::info
Requires the `accounts:read` OAuth2 scope.
:::

## Query parameters

- `account_id` string, required

## Response `200`

Data processing settings

- object
  - `data` DataProcessingSettingsV1, required
    - `type` 'data_processing_settings', required
    - `id` string, required — The account ID this configuration belongs to.
    - `attributes` object, required
      - `enabled` boolean, nullable, required — Whether third-party data enrichment providers are allowed for this account. `null` means the setting has never been explicitly configured.
      - `changelog` object[], required — Full change history ordered most-recent-first. Each entry records the value set, who set it, and when.
        - `enabled` boolean, required — The value that was set in this change.
        - `changed_by_email` string, email, required — Email address of the user who made the change.
        - `changed_by_name` string, required — Full name of the user who made the change.
        - `changed_at` string, date-time, required — ISO 8601 timestamp of when the change was made.
  - `meta` object, required
    - `request_id` string, required — A unique identifier assigned to each API request for end-to-end traceability.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized. The request was rejected because the credentials are missing, invalid, expired, or have been revoked. The client must re-authenticate before retrying. Clients can differentiate via the `code` value of the first item in `errors`.
- `403` — Forbidden. The credentials are valid but the caller is not authorized to perform the request — typically because the user lacks the required permission, the OAuth scope is insufficient, the subscription plan does not include the required entitlement, the `account_id` does not belong to the authenticated user, or the target list is read-only and its members cannot be modified. Clients can differentiate via the `code` value of the first item in `errors`.
- `429` — Too many requests. Either the per-second rate limit or the monthly quota configured for the API key / OAuth application has been exceeded. Clients can differentiate via the `code` value of the first item in `errors`.
- `500` — Internal server error
- `504` — Server timeout

## Changes

> 17 revisions in range; 1 not diffed.

- **2026-09-01** `885dcce2a6c2` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/leadfeeder/apis/leadfeeder-public-api/changes/v1/settings/data-processing/get.md)

---

[API](https://skmtc.dev/leadfeeder/apis/leadfeeder-public-api.md) · [All operations](https://skmtc.dev/leadfeeder/apis/leadfeeder-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/leadfeeder/leadfeeder-public-api/revisions/885dcce2a6c2/schema)