/projects/Required permission: projects:write. All records and related selectors must remain inside the key's selected access targets.
- Required permissions
projects:write- Available scopes
- Entire Portal or Selected source channels
Headers and URL parameters
| Name | Location | Type | Required |
|---|---|---|---|
Idempotency-KeyView parameter schema | header | string | Yes |
Request body
application/json · Required body
| Field | Type | Required |
|---|---|---|
business_id | string | Yes |
create_funding_requestAlso create a client funding request sharing this Project’s matching workspace. Requires source ownership, a live client relationship, and enabled client matchmaking and funding-request creation. Does not invite anyone. Cannot be combined with service_request_id. | boolean | No |
decision_due_date | string or null | No |
flexibility_notes | string | No |
name | string | No |
purpose | string | No |
service_request_idContinue an authorized client request returned by GET /businesses/{business_id}/activation/, preserving its matching work. Send business_id and service_request_id only. | string | No |
target_amount | string or number or null | No |
target_currency | string or null | No |
View request schema
Example request
curl --request POST \
--url "https://api.staging.levr.ai/v1/projects/" \
--header "Authorization: Bearer $LEVR_API_KEY" \
--header "Idempotency-Key: $IDEMPOTENCY_KEY" \
--header "Content-Type: application/json" \
--data "@request.json"curl --request POST \
--url "https://api.staging.levr.ai/v1/projects/" \
--header "Authorization: Bearer $LEVR_API_KEY" \
--header "Idempotency-Key: $IDEMPOTENCY_KEY" \
--header "Content-Type: application/json" \
--data '{
"business_id": "biz_2m8q7c9k4x6p3n5d",
"name": "Growth financing intake"
}'Responses
| Status | What it means |
|---|---|
201 | 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 |
