Trigger domain verification
App Domains
Trigger domain verification
Re-runs the DNS verification check for a custom domain. Caller is expected to have already configured the TXT record at _migetapp-verify.<domain> with the value from `verification_token`. The check runs asynchronously (Sidekiq worker `VerifyDomain` with Fibonacci backoff up to 60 minutes); poll the show endpoint to track status. If the domain is already verified, the call is a no-op and returns the current state. If the domain doesn't need verification (e.g. www subdomain whose root is verified), the call returns the current state without scheduling work.
POST
Trigger domain verification
Authorizations
Bearer token for authentication. Format: 'Bearer {token}'
Headers
Workspace ID (uses default workspace if not provided)
Path Parameters
Application UUID
Unique domain identifier (UUID)
Response
Trigger domain verification
Api_V1_Entities_Domain model
Unique domain identifier
Domain name
DNS CNAME target — populated only after verification succeeds
Verification state: 'pending', 'in_progress', 'verified', or 'failed'
Token to publish as TXT _migetapp-verify.. Populated only while verification is needed; cleared once verified.
Creation timestamp
Last update timestamp

