# Read a lender's API connection

How this workspace reaches one Lenders record's submission API (SmartBiz, Bitty, PIRS, Spectra, Lendr, ECG, Credibly): `provider`, `endpoint`, `enabled`, and which credentials are on file — `apiKeyConfigured` with the key's last four, `brokerIdConfigured`, `portalCredentialsConfigured`. The credentials themselves are write-only and never answered. 404 when the lender has no connection; then a send to a lender whose record names a portal or API is refused `lender_api_not_connected`. Lenders pages only.

Access class: `def:read`.

## Endpoint

`GET /v1/definitions/{key}/rows/{rowId}/api-connection`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| key | path | string | Yes |
| rowId | path | string | Yes |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "apiKeyConfigured": true,
    "apiKeyLast4": "string",
    "brokerIdConfigured": true,
    "enabled": true,
    "endpoint": "string",
    "lenderRowId": "",
    "portalCredentialsConfigured": true,
    "provider": "string",
    "updatedAt": "2026-01-01T00:00:00Z",
    "updatedByAccountId": ""
  }
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```
