---
title: "POST /api/notifications/deployments/{deploymentId}/wiz/validate"
method: POST
path: "/api/notifications/deployments/{deploymentId}/wiz/validate"
tags: ["WizCredentialService"]
---

# POST /api/notifications/deployments/{deploymentId}/wiz/validate

`POST /api/notifications/deployments/{deploymentId}/wiz/validate`

## Path parameters

- `deploymentId` integer, required

## Request body

- ProtosNotificationsV1ValidateWizCredentialRequest
  - `deploymentId` integer
  - `clientId` string
  - `clientSecret` string
  - `apiUrl` string
  - `tokenUrl` string
  - `id` string — Existing credential to validate. When set and no client_secret is provided, the stored secret is validated server-side, so clients can test a saved credential without sending (or knowing) the secret. When a client_secret is provided, that secret is validated instead.

## Response `200`

OK

- ProtosNotificationsV1ValidateWizCredentialResponse
  - `valid` boolean
  - `error` string

---

[API](https://skmtc.net/semgrep/apis/semgrep-web-app.md) · [All operations](https://skmtc.net/semgrep/apis/semgrep-web-app/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/semgrep/semgrep-web-app/versions/6483eeecd582/schema)