---
title: "Match"
method: POST
path: "/entity-match/match"
tags: ["Match"]
---

# Match

`POST /entity-match/match`

Resolve human-readable entity names to Recorded Future entity IDs using fuzzy matching, with an optional type filter to narrow results to specific entity categories.

## Request body

- object
  - `name` string, required — This mandatory free text search field is used to match against entity names.
  - `type` string[] — An array of types is optional. If in use, the **Match** operation will only try to match on entities that meet **any** of the "type" criteria. See the list of [Available Entity Types](https://recorded-future.readme.io/reference/available-entity-types).
  - `limit` integer — This optional field is used to limit the max number of responses returned (maximum 100).

## Response `200`

Successful request - Returns a list of items or an empty list if no items were found.

- EntityMatchResponse[]
  - `id` string, required — Recorded Future entity ID (use with Lookup and other endpoints)
  - `name` string, required — Entity display name (may differ from search term)
  - `type` string, required — Entity type (e.g., CyberVulnerability, Malware, IpAddress, InternetDomainName)

## Other responses

- `400` — Bad request
- `401` — Unauthorized

---

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