Create client intake

Read as Markdown

POST/businesses/{business_id}/client-intake/

Creates or returns intake in the business's source workspace using the effective published lead source template. Works when automatic source intake is off. Preserves existing projects and Business metadata. Sends no invitation; review the intake before using its share endpoint. Requires Businesses write access.

Parameters

Name	Location	Type	Required
business_id View parameter schema	path	string	Yes
Idempotency-Key View parameter schema	header	string	Yes

Example request

cURLCopy

curl --request POST \
  --url "https://api.levr.ai/v1/businesses/$BUSINESS_ID/client-intake/" \
  --header "Authorization: Bearer $LEVR_API_KEY" \
  --header "Idempotency-Key: $IDEMPOTENCY_KEY"

Responses

Status	What it means
200	Existing intake returned. View response headers application/json View response schema Illustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response
201	Intake created. View response headers application/json Same response body as 200.
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
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