> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/platform-api/data-world-model/entity-resolve.md).

# Entity Resolve

Resolve a polymorphic identifier to ranked entity candidates.

Entity resolve looks up entities by phone number, email, canonical identifier, external-system identifier, entity UUID, or a combination of identifiers. It powers inbound caller identification, webhook matching, and other workflows that need to turn an external identifier into a workspace entity.

## Resolve an Entity

{% openapi src="<https://platform.api-us.concurrence.com/v1/openapi.json>" path="/v1/{workspace\_id}/world/entities/resolve" method="post" %}
<https://platform.api-us.concurrence.com/v1/openapi.json>
{% endopenapi %}

At least one identifier is required. An external-system identifier is system-qualified: resolution checks canonical keys for supported resource types and the bare value used by producers that minted it as a canonical identifier. An external ID that was never minted into the canonical map is not resolvable through this operation.

## Ranking

Candidates are ranked by identifier-match confidence and then by the number of identifiers that matched. A direct UUID match has confidence `1.0`; at the same confidence, a row matching both phone and email ranks above one matching only phone. This ranking uses identifier-match weights, not the world-event source classes described in [Confidence as Trust Architecture](/developer-guide/platform-api/data-world-model.md#confidence-as-trust-architecture). It is neither a calibrated probability of identity nor a substitute for identity verification.

## Example

```json
{
  "entity_type": "person",
  "phone": "+15551234567",
  "email": "jane@example.com",
  "limit": 5
}
```

Requests without an identifier return `400`; malformed values return `422`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/developer-guide/platform-api/data-world-model/entity-resolve.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.