Replace Deal participants

PUT/deals/{deal_id}/participants/

Required permission: deals:write. All records and related selectors must remain inside the key's selected access targets.

Required permissions: deals:write
Available scopes: Entire Portal or Selected source channels

Headers and URL parameters

Name	Location	Type	Required
`deal_id` View parameter schema	path	string	Yes
`If-Match` View parameter schema	header	string	Yes
`Idempotency-Key` View parameter schema	header	string	Yes

Request body

application/json · Required body

Field	Type	Required
`new_people`Create and attach contacts within this record using its Write permission. Email is normalized; an existing contact already reachable in the selected scope is reused without changing stored fields. Contacts outside that scope are rejected. The combined set replaces the current relationships. Returns only Person references; reading or editing contact details requires People permission.	array	No
`person_ids`	array	Yes
`primary_person_id`	See schema	No

View request schema

Example request

curl --request PUT \
  --url "https://api.staging.levr.ai/v1/deals/$DEAL_ID/participants/" \
  --header "Authorization: Bearer $LEVR_API_KEY" \
  --header "If-Match: $IF_MATCH" \
  --header "Idempotency-Key: $IDEMPOTENCY_KEY" \
  --header "Content-Type: application/json" \
  --data "@request.json"

curl --request PUT \
  --url "https://api.staging.levr.ai/v1/deals/$DEAL_ID/participants/" \
  --header "Authorization: Bearer $LEVR_API_KEY" \
  --header "If-Match: $IF_MATCH" \
  --header "Idempotency-Key: $IDEMPOTENCY_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "person_ids": [
    "pers_2m8q7c9k4x6p3n5d"
  ]
}'

Responses

Status	What it means
`200`	Successful response. View response headers `application/json` View response schema Illustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response
`400`	Correct the request fields and try again. View response headers `application/json` View response schema Illustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response
`401`	Provide a valid API key and try again. View response headers `application/json` View response schema Illustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response
`403`	This API key does not allow the requested action. View response headers `application/json` View response schema Illustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response
`404`	The requested resource was not found or is not available to this API key. View response headers `application/json` View response schema Illustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response
`409`	The request conflicts with the resource's current state. Refresh it before trying again. View response headers `application/json` View response schema Illustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response
`412`	The request was not completed. View response headers `application/json` View response schema Illustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response
`429`	Too many requests were sent. Wait before trying again. View response headers `application/json` View response schema Illustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response
`500`	Levr could not complete the request. Keep the request ID and retry when safe. View response headers `application/json` View response schema Illustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response

Copy instructions to your AI agent

Request an integration