---
title: "Complete client portal wait step"
method: POST
path: "/v1/cases/{id}/complete-client-portal-wait-step"
tags: ["Client portal"]
---

# Complete client portal wait step

`POST /v1/cases/{id}/complete-client-portal-wait-step`

On a case in `draft` status, mark wait steps of client portal as completed

---

#### See also  
Learn more about [Cases](./cases-guide)

## Path parameters

- `id` string, uuid, required

## Request body

- CompleteClientPortalWaitStepInput
  - `client_portal_id` string, uuid — Optional client portal id to only complete its own wait step. If not specified, all the wait steps of all client portals will be completed.
  - `wait_step_key` string — Optional wait step key to only complete this specific step. If not specified, all the pending wait steps will be completed.

## Response `200`

**ℹ️ Click to see full payload**

- CompleteClientPortalWaitStepResponse
  - `completed_wait_step_keys` string[], required — List of wait step keys that were completed

## Other responses

- `400` — The request is either malformed or contain invalid parameters. - Make sure the identifier specified in the URL is a valid UUID - Make sure the body payload matches the expected schema - Case status is not `draft`
- `404` — No case can be found.

---

[API](https://skmtc.dev/dotfile/apis/api-specifications.md) · [All operations](https://skmtc.dev/dotfile/apis/api-specifications/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/dotfile/api-specifications/revisions/36393567057b/schema)