---
title: "Create FindSummary"
method: POST
path: "/findSummary"
tags: ["FindSummary"]
---

# Create FindSummary

`POST /findSummary`

## Request body

- FindSummary
  - `id` string — The ID of the FindSummary matching it's BQ id. This is the same as the selector override's selector_variant_id.
  - `selector_id` string, required — The ID of the FindSummary's selector id
  - `environment_id` string, required — The environment id that the find strategy ran under
  - `deployment_id` string — The deployment id that the find strategy ran under
  - `journey_id` string — The journey id that the find strategy ran under
  - `journey_invariant_id` string — The journey invariant id that the find strategy ran under
  - `journey_run_id` string — The id of the journey run that generated the find summary
  - `step_id_in_journey` string — Step id relative to journey
  - `step_id_in_flow` string — Step id relative to flow
  - `step_run_id` string — The unique id for each time the step is run
  - `created_time` integer, required — Time at which the FindSummary was created
  - `organization_id` string — The ID of the organization associated with this FindSummary
  - `find_strategy_id` string — The find strategy used
  - `located_with_properties` string[] — The list of properties the element was located with
  - `locators_candidate_count` object — The locator candidates and their counts which are expected to match for a correct identification of the element
  - `found_selector` string — The selector of the element found using this strategy
  - `matcher_mismatches` string[] — The selector matchers (string id) that did not match between selector used and the element found/chosen, if successful
  - `matcher_candidate_count` object — Map from selector matchers (string id) used to number of candidate elements that matched
  - `matcher_similarity` unknown
  - `hypothesis_requires_confirmation` boolean — Whether the element found is a hypothesis requiring confirmation (auto-heal)
  - `browser` string — The browser of the find strategy ran in
  - `emulation_mode` string — Desktop or mobile web emulation under which the find strategy ran
  - `device_emulation_id` string — Device ID with which the find strategy ran
  - `device_emulation_preset_type` string — Device preset type with which the find strategy ran
  - `selector_type` string
  - `find_type` string
  - `candidate_matches` integer — The number of candidate matches to the selector found by the final find strategy
  - `valid_matches` integer — The number of candidate matches to the selector that were deemed valid by the final find strategy
  - `find_start_time` integer — The time when the find action began
  - `final_strategy_start_time` integer — The time when the find strategy that generated the result began
  - `first_found_time` integer — The time when the found element was first located
  - `first_found_time_from_start_ms` integer — Milliseconds since the start of the find action when the found element was first located
  - `found_score` number, double — The score given to the found element by the successful find strategy

## Response `201`

The FindSummary that was created

- FindSummary
  - `id` string — The ID of the FindSummary matching it's BQ id. This is the same as the selector override's selector_variant_id.
  - `selector_id` string, required — The ID of the FindSummary's selector id
  - `environment_id` string, required — The environment id that the find strategy ran under
  - `deployment_id` string — The deployment id that the find strategy ran under
  - `journey_id` string — The journey id that the find strategy ran under
  - `journey_invariant_id` string — The journey invariant id that the find strategy ran under
  - `journey_run_id` string — The id of the journey run that generated the find summary
  - `step_id_in_journey` string — Step id relative to journey
  - `step_id_in_flow` string — Step id relative to flow
  - `step_run_id` string — The unique id for each time the step is run
  - `created_time` integer, required — Time at which the FindSummary was created
  - `organization_id` string — The ID of the organization associated with this FindSummary
  - `find_strategy_id` string — The find strategy used
  - `located_with_properties` string[] — The list of properties the element was located with
  - `locators_candidate_count` object — The locator candidates and their counts which are expected to match for a correct identification of the element
  - `found_selector` string — The selector of the element found using this strategy
  - `matcher_mismatches` string[] — The selector matchers (string id) that did not match between selector used and the element found/chosen, if successful
  - `matcher_candidate_count` object — Map from selector matchers (string id) used to number of candidate elements that matched
  - `matcher_similarity` unknown
  - `hypothesis_requires_confirmation` boolean — Whether the element found is a hypothesis requiring confirmation (auto-heal)
  - `browser` string — The browser of the find strategy ran in
  - `emulation_mode` string — Desktop or mobile web emulation under which the find strategy ran
  - `device_emulation_id` string — Device ID with which the find strategy ran
  - `device_emulation_preset_type` string — Device preset type with which the find strategy ran
  - `selector_type` string
  - `find_type` string
  - `candidate_matches` integer — The number of candidate matches to the selector found by the final find strategy
  - `valid_matches` integer — The number of candidate matches to the selector that were deemed valid by the final find strategy
  - `find_start_time` integer — The time when the find action began
  - `final_strategy_start_time` integer — The time when the find strategy that generated the result began
  - `first_found_time` integer — The time when the found element was first located
  - `first_found_time_from_start_ms` integer — Milliseconds since the start of the find action when the found element was first located
  - `found_score` number, double — The score given to the found element by the successful find strategy

## Other responses

- `400` — Invalid or missing parameter
- `401` — User not authenticated
- `403` — User not authorized
- `default` — Unknown error

---

[API](https://skmtc.net/mabl/apis/mabl-api.md) · [All operations](https://skmtc.net/mabl/apis/mabl-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mabl/mabl-api/revisions/d0fc0114da66/schema)