/deal-applications/{application_id}/mark-not-submitted/Read decision options first. Send the application ETag in If-Match, its answers_revision as expected_answers_revision, and a new Idempotency-Key. Copy only email and origin for each selected recipient from the returned list; [] sends no optional communications. Shared status, history, stage synchronization, automatic notifications and configured stage email automations still apply. Identical retries return the original result. An optional destination_stage_id must be in your Deal's pipeline and match the resulting application status. If omitted, the Deal uses your Portal's matching outcome stage, creating the default stage when needed; other Portals follow their synchronization preferences. Available only before an actual submission; it does not undo submission.
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
application_idView parameter schema | path | string | Yes |
If-MatchView parameter schema | header | string | Yes |
Idempotency-KeyView parameter schema | header | string | Yes |
Request body
Send a body that matches the published schema.
View request schema
Example request
curl --request POST \
--url "https://api.levr.ai/v1/deal-applications/$APPLICATION_ID/mark-not-submitted/" \
--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 POST \
--url "https://api.levr.ai/v1/deal-applications/$APPLICATION_ID/mark-not-submitted/" \
--header "Authorization: Bearer $LEVR_API_KEY" \
--header "If-Match: $IF_MATCH" \
--header "Idempotency-Key: $IDEMPOTENCY_KEY" \
--header "Content-Type: application/json" \
--data '{
"expected_answers_revision": 3,
"recipients": [
{
"email": "broker@example.com",
"origin": "organization"
}
]
}'Responses
| Status | What it means |
|---|---|
200 | Successful response. View response headers
View response schemaIllustrative 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
View response schemaIllustrative 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
View response schemaIllustrative 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
View response schemaIllustrative 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
View response schemaIllustrative 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
View response schemaIllustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response |
412 | The request was not completed. View response headers
View response schemaIllustrative 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
View response schemaIllustrative 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
View response schemaIllustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response |
