iam.sso-connections.verify-domain

Look up the TXT record and mark the domain verified when it matches

POST /iam/api/sso-connections/{id}/domains/{domainId}/verifyIAM iam:VerifySsoDomainChanges state

Request syntax

POST /iam/api/sso-connections/{id}/domains/{domainId}/verify

Path parameters

  • idRequired

    string

    Constraints: uuid

  • domainIdRequired

    string

    Constraints: uuid

Response

200 with { verified, found }: whether the expected value was published, and up to 10 TXT values found at the record’s name. 502 when DNS could not be asked; try again a minute later.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow iam:VerifySsoDomain on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud iam sso-connections verify-domain id domainId

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_iam_sso-connections_verify-domain.