List matchmaking application autofill suggestions

Read as Markdown

GET/project-matchmaking-application-autofill-runs/{run_id}/suggestions/

Review a cursor-paginated page of persisted proposed values and evidence. Review one pending suggestion's proposed value, evidence, and concerns. Read the current answers, then POST to the Run's suggestions_url plus {suggestion_id}/accept/ with no request body, the answer ETag in If-Match, and a unique Idempotency-Key. Levr checks the answer revision and target drift, applies the proposal, and records acceptance in one transaction. A 412 means the answers changed; reread and review before issuing a new command. A 409 suggestion_conflict means the suggestion is stale, superseded, or already resolved; refresh suggestions and review again. An identical retry must reuse the original precondition and key. Check the returned suggestion is accepted and verify the intended value through the answers read. Use the returned ETag for the next answer mutation. Do not copy proposal metadata into an answer-update request to accept a suggestion.

Parameters

Name	Location	Type	Required
run_id View parameter schema	path	string	Yes
searchSearch section, question, field labels, and source excerpts. View parameter schema	query	string	No
statusFilter by one status, ignoring letter case: pending, accepted, dismissed, stale, failed. View parameter schema	query	string	No
orderingComma-separated display_order, created_at, updated_at, or status; prefix - for descending. Defaults to display_order,created_at. View parameter schema	query	string	No
page_size View parameter schema	query	integer	No
cursor View parameter schema	query	string	No

Example request

cURLCopy

curl --request GET \
  --url "https://api.levr.ai/v1/project-matchmaking-application-autofill-runs/$RUN_ID/suggestions/" \
  --header "Authorization: Bearer $LEVR_API_KEY"

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