---
title: "Update payment status"
method: POST
path: "/api/v1/apps/custom-invoicing/{invoiceId}/payment/status"
tags: ["App: Custom Invoicing"]
---

# Update payment status

`POST /api/v1/apps/custom-invoicing/{invoiceId}/payment/status`

## Path parameters

- `invoiceId` string, required

## Request body

- CustomInvoicingUpdatePaymentStatusRequest — Update payment status request. Can be used to manipulate invoice's payment status (when custominvoicing app is being used).
  - `trigger` 'paid' | 'payment_failed' | 'payment_uncollectible' | 'payment_overdue' | 'action_required' | 'void', required — Payment trigger to execute on a finalized invoice.

## Response `204`

There is no content to send for this request, but the headers may be useful.

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
- `401` — The request has not been applied because it lacks valid authentication credentials for the target resource.
- `403` — The server understood the request but refuses to authorize it.
- `412` — One or more conditions given in the request header fields evaluated to false when tested on the server.
- `500` — The server encountered an unexpected condition that prevented it from fulfilling the request.
- `503` — The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay.
- `default` — An unexpected error response.

---

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