---
title: "Get Status of Automatching Task"
method: GET
path: "/receipts/automatching/{automatchingTaskId}"
tags: ["Receipt Automatching"]
---

# Get Status of Automatching Task

`GET /receipts/automatching/{automatchingTaskId}`

Query the status of the automatching task specified by path parameter `automatchingTaskId`.

## Path parameters

- `automatchingTaskId` string, uuid, required

## Response `200`

Ok

- object
  - `automatchingTaskId` string, uuid, required — The id of the automatching task.
  - `organizationId` string, uuid, required — The id of the organization this task belongs to.
  - `matchedTransactions` object[] — The transactions that were matched to the provided data. Can also be empty, if no match was found. In most cases this contains 0..1 matches, but some receipts or invoices refer to more than one transaction. This is then reflected here.
    - `transactionId` string, uuid, required — The id of the transaction that is a possible match to the provided data.
    - `score` number, float, required — The score (from 0..1) of this match. The higher the score, the more likely the match is correct.
  - `status` 'IN_PROGRESS' | 'ERROR_DURING_PROCESSING' | 'ERROR_FEATURE_NOT_ACTIVE' | 'MATCHING_TRANSACTION_FOUND' | 'MATCHING_TRANSACTION_NOT_FOUND', required — The status of the automatching task.
  - `additionalInformation` string — Additional information about the status. E.g. a more detailed error message or a reason why no match was found.

## Other responses

- `400` — unresolved $ref
- `401` — unresolved $ref
- `403` — unresolved $ref
- `404` — unresolved $ref
- `500` — unresolved $ref

---

[API](https://skmtc.dev/getpliant/apis/pliant-customer-api.md) · [All operations](https://skmtc.dev/getpliant/apis/pliant-customer-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/getpliant/pliant-customer-api/revisions/f3f589cfa718/schema)