# Unlink a vendor from QuickBooks

```http
DELETE https://secure.yoprint.com/v1/api/store/{team_slug}/vendor/{hash_id}/external_id/{id}
```

- API version: v1
- Operation ID: `v1_public_vendor_external_id_delete`
- Section: Purchasing › [Vendors](https://developer.yoprint.com/reference/vendors.md)
- Web page: https://developer.yoprint.com/reference/vendors/v1-vendor-external-id-delete/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Removes the link between this vendor and its QuickBooks Online vendor for the connection `{id}`. Nothing changes in QuickBooks. Answers `success: true` with `data: null`, also when nothing was linked or `{id}` is no integration of the team.

## Permission

Any member of the team.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.
- `hash_id` (string, required): The vendor's id (`id` from List vendors). A hash id from an earlier answer; unique keys and document numbers (such as `PO0042`) don't work here. Example `EDhVUaC6jbLbed`.
- `id` (string, required): The QuickBooks Online connection's id (`id` from List integrations), not the QuickBooks record's Id. A hash id from an earlier answer; unique keys and document numbers (such as `PO0042`) don't work here. Example `uAu3dAKIaHyAYk`.

## Request body

This operation takes no request body.

### Example request

```bash
curl -X DELETE 'https://secure.yoprint.com/v1/api/store/your-team/vendor/EDhVUaC6jbLbed/external_id/uAu3dAKIaHyAYk' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1'
```

## Response

`200` Successful response.

Fields:

- `data` (null, required)
- `status` (integer, required)
- `success` (boolean, required)

Example response:

```json
{
  "data": null,
  "status": 200,
  "success": true
}
```

## Errors

- `401` The API key is missing or wrong (`unauthenticated`).
- `403` You are not allowed to do this. `api_access_not_in_plan`: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only `{"message": "Insufficient Permission"}`. Other refusals use the error envelope, with `unauthorized` or `user_is_not_authorized`.
- `404` Not found. `page_not_found`: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's. `code: null`, with a message that starts "No query results for": there is no record with that id.

## Related

- [Link a vendor to a QuickBooks vendor](https://developer.yoprint.com/reference/vendors/v1-vendor-external-id-update.md): `PUT /v1/api/store/{team_slug}/vendor/{hash_id}/external_id/{id}`