Verify Domain

post

https://{region}.api.jamfcloud.com/sso/v1/domains/{domainId}/actions/verify

Checks the domain's DNS records for the TXT record matching its verificationKey and returns the domain with the outcome in domainStatus: VERIFIED when the record was found, and the previous status when it was not. A failed check is not an error response — inspect domainStatus.

DNS propagation is not instant, so a check that runs immediately after the record is published can legitimately fail. Verification is rate limited to once every five minutes, except for the first attempt on a newly added domain; an attempt inside that window is rejected with 400.

The request has no body. A domain another organization has already verified is rejected with 409.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

Language

Credentials

OAuth2

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200The domain, with domainStatus reflecting the outcome of the check.

400Bad Request. A verification attempt was made inside the five-minute rate limit window — wait and try again — or domainId is not a valid domain identifier.

401Unauthorized. The access token is missing, invalid, or expired. The API Gateway rejects the request before it reaches the service.

403Forbidden. The domain belongs to a different organization, or it is shared to this organization but cannot be changed by it.

404Not Found. No such domain exists for this organization.

409Conflict. The domain is already claimed by this organization, or it has already been verified by a different organization. A domain can only be verified by one organization at a time.

500Internal Server Error. The organization in the token could not be resolved, or an upstream dependency failed. The description is deliberately generic; quote traceId when reporting the failure.