---
title: "Update Partner Submission Status (Multiple)"
method: POST
path: "/transactions/partner-submission-status"
tags: ["Transactions"]
---

# Update Partner Submission Status (Multiple)

`POST /transactions/partner-submission-status`

Updates the partnerSubmissionStatus of one or more transactions. See [documentation](/docs/transaction-entity#partner-submission-status) for more information.

## Request body

- object
  - `partnerSubmissionStatus` 'NOT_SYNCED' | 'SYNCED' | 'TEMP_LOCKED' | 'LOCKED', required — The status `NOT_SYNCED` is the default status of a transaction, it can be changed to `SYNCED` by the partner, e.g. if the partner consumed a transaction successfully. The status `TEMP_LOCKED` makes the transaction immutable for cardholders within Pliant's apps - it is a reversible status and can be changed back to `SYNCED`. `LOCKED` makes a transaction immutable for all users. `LOCKED` is the final status which cannot be modified anymore.
  - `transactionIds` string[], required — The unique identifiers of the transactions.

## Response `202`

Ok

## Other responses

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

---

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