Deals

Stop excluding an investor or team from a deal

DELETE/deals/{id}/exclusions/{member_id}

Removes the exclusion of the investor or team and returns 204, also when there was none, so a retry is safe. It does not bring back a show rule the exclusion replaced, and never takes back folder access already granted. Same 409 rule as adding, but only when it would remove something: removing an exclusion that is not there returns 204 on a deal in any status. No dry run. Emits deal.updated with exclusions in changed_fields; no email. The POST undoes it.

Path parameters

  • idstring (uuid)Required#

    The record's id.

  • member_idstring (uuid)Required#

    The id of the investor or team to stop excluding.

Responses

204

The investor or team is no longer excluded through this set.

401

Authentication failed. error.code is one of invalid_token, expired, revoked.

Error
403

Authorization failed. error.code is one of org_disabled, ip_blocked, missing_scope, scope_disabled, user_disabled.

Error
404

Resource not found (error.code = not_found).

Error
409

The request conflicts with existing state (error.code = conflict), e.g. a compliance flow with the requested name already exists.

Error
422

The request can't be processed (HTTP 422): validation_failed with one ErrorDetail per problem, or a code documented on the operation.

Error
429

Rate limit exceeded (error.code = rate_limited).

Error

Examples

curl -X DELETE https://your-org-domain/kong/core/api/v2/deals/{id}/exclusions/{member_id}\
  -H "Authorization: Bearer $HELM_API_KEY"\
  -H "Content-Type: application/json"