Create linked client funding request

POST/projects/{project_id}/funding-request/

Make this Project's existing matching workspace available as a client funding request. Preserves Criteria, answers, matching results, and selections. Requires source-provider ownership, an active client relationship, enabled client matchmaking, and funding-request creation capability. No invitation is sent and private Project fields are not copied. Returns 201 when linked, or 200 when already linked. Use the Project ETag from GET /projects/{project_id}/.

Required permissions

projects:write

Available scopes

Entire Portal or Selected source channels

Headers and URL parameters

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

Example request

cURLCopy

curl --request POST \
  --url "https://api.staging.levr.ai/v1/projects/$PROJECT_ID/funding-request/" \
  --header "Authorization: Bearer $LEVR_API_KEY" \
  --header "Idempotency-Key: $IDEMPOTENCY_KEY" \
  --header "If-Match: $IF_MATCH"

Responses

Status	What it means
200	An existing request is already linked. View response headers application/json View response schema Illustrative data. Use the identifiers, cursors, and URLs returned by your requests. View example response
201	Successful response. 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
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