---
title: "Connect Salesforce with a customer Connected App"
method: POST
path: "/v1/integrations/salesforce/connect"
tags: ["integrations"]
---

# Connect Salesforce with a customer Connected App

`POST /v1/integrations/salesforce/connect`

Connect a Salesforce org using a customer-created Connected App (client-credentials flow, no OAuth).

## Request body

- SalesforceManualConnectBody — Request body for connecting Salesforce with a customer Connected App (client-credentials flow).
  - `client_id` string, required — Connected App consumer key
  - `client_secret` string, required — Connected App consumer secret
  - `my_domain_url` string, required — The org's My Domain URL (https://<domain>.my.salesforce.com)
  - `store_name` string, nullable — Optional ingestion store name
  - `sync_schedule_interval` 'off' | 'ten_minutes' | 'hourly' | 'daily' | 'weekly' — Initial periodic sync interval

## Response `200`

The connected Salesforce installation

- IntegrationInstallationResponse — Integration installation response.
  - `data` IntegrationInstallation, required — Service-level representation of an installed provider integration.
    - `id` string, required — The integration installation ID
    - `created_at` string, date-time, required — The creation time
    - `updated_at` string, date-time, required — The last update time
    - `organization_id` string, required — The organization ID
    - `provider` string, required — The integration provider identifier
    - `external_account_id` string, required — The provider workspace/account ID
    - `external_account_name` string, nullable, required — The provider workspace/account name
    - `installed_by_user_id` string, nullable, required — The Mixedbread user who installed the provider
    - `status` string, required — The installation status
    - `scopes` string[], nullable, required — Granted provider scopes
    - `metadata` object, required — Provider-specific metadata

## Other responses

- `409` — The external account is already connected to a different Mixedbread organization
- `422` — The request failed validation, or the credentials it carries were rejected

## Changes

- **2026-09-21** `b12f43c90ba3` — 2 warning
  - added the new `bucket_unavailable_error` enum value to the `code/anyOf[subschema #1: ErrorCode]/` response property for the response status `409`
  - added the new `bucket_unavailable_error` enum value to the `code/anyOf[subschema #1: ErrorCode]/` response property for the response status `422`
- **2026-09-15** `957bf8ec8df8` — 2 warning
  - added the new `store_frozen_error` enum value to the `code/anyOf[subschema #1: ErrorCode]/` response property for the response status `409`
  - added the new `store_frozen_error` enum value to the `code/anyOf[subschema #1: ErrorCode]/` response property for the response status `422`
- **2026-09-10** `adde8ecfa74f` — 1 warning, 4 info
  - removed the optional property `detail` from the response with the `422` status
  - added the non-success response with the status `409`
  - added the required property `code` to the response with the `422` status
  - added the required property `message` to the response with the `422` status
  - …1 more

[Change history](https://skmtc.dev/mixedbread/apis/mxbai-omni/changes/v1/integrations/salesforce/connect/post.md)

---

[API](https://skmtc.dev/mixedbread/apis/mxbai-omni.md) · [All operations](https://skmtc.dev/mixedbread/apis/mxbai-omni/llms.txt) · [OpenAPI document](https://skmtc.dev/mixedbread/apis/mxbai-omni/revisions/824e59bfac1e?raw)