---
title: "Trigger a matching run"
method: POST
path: "/v1/matching/contexts/{contextId}/run"
tags: ["Matching"]
---

# Trigger a matching run

`POST /v1/matching/contexts/{contextId}/run`

Use this endpoint to trigger a matching run for a reconciliation context. You can use DRY_RUN mode to test rules without committing results, or COMMIT mode to persist matches.

## Path parameters

- `contextId` string, required

## Headers

- `X-Request-Id` string
- `X-Idempotency-Key` string

## Request body

- RunMatchRequest
  - `mode` 'DRY_RUN' | 'COMMIT', required

## Response `202`

Indicates that the request was accepted for processing.

The response includes the `X-Idempotency-Replayed` header.

If the value is false, the request was just processed. If the value is true, the response is a replay of a previously processed request.

See [Retries and idempotency](/en/reference/retries-idempotency) for more details.

- RunMatchResponse
  - `runId` string, uuid
  - `status` 'PROCESSING' | 'COMPLETED' | 'FAILED'

## Other responses

- `400` — The request contains invalid parameters or payload.
- `401` — The request lacks valid authentication credentials.
- `403` — You do not have permission to access this resource.
- `404` — The requested resource was not found.
- `500` — An unexpected error occurred on the server.

---

[API](https://skmtc.net/lerian/apis/identity-plugin.md) · [All operations](https://skmtc.net/lerian/apis/identity-plugin/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lerian/identity-plugin/versions/25daba385532/schema)