# Check a business for ISO conflicts

Asks whether this merchant has ALREADY been submitted to this lender, and whether it was somebody else who sent it — the conflict check before a file goes out, so two brokers do not shop the same deal to the same funder. Body: `merchantKey` and `lenderTenantId`, the lender's linked workspace from `get_lender-workspaces`. A POST rather than a GET because the merchant identifier is the question's body, and a merchant's name does not belong in a URL that proxies and access logs keep. The answer names no other broker.

Access class: `workspace`.

## Endpoint

`POST /v1/iso-conflict-checks`

## Request body

Content type: `application/json`.

```json
{
  "body": {
    "lenderTenantId": 1,
    "merchantKey": "string"
  },
  "params": {},
  "query": {}
}
```

## Responses

### 201

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "conflict": true,
    "lenderTenantId": 1,
    "merchantKey": "string",
    "mine": 1,
    "others": 1,
    "statuses": [
      "string"
    ]
  }
}
```

### 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"
}
```