Return domains
Your own app's hostname, such as charge.example.com, where an API payment's return_url may send the driver after hosted checkout. Proven by one TXT record at _ivora-return.<hostname> holding the domain's own token: no address record, certificate or edge setup, so the app stays wherever it is hosted. Ivora never serves, proxies or routes a return domain. It is ready (dns_verified) while the record checks out; Ivora rechecks it every 15 minutes, stops accepting it once the record is gone, and a verification older than an hour no longer counts. A hostname has one verified owner across tenants and purposes. Exact hostname only: no wildcard, parent or subdomain. Requires stations:read or stations:write.
5 endpoints
- getList custom return domains and DNS/TLS readiness/v1/tenants/{tenant_id}/return-domains
- postPrepare a tenant return domain and its two DNS records/v1/tenants/{tenant_id}/return-domainsIdempotent by tenant and normalized hostname.
- getRead one return domain setup/v1/tenants/{tenant_id}/return-domains/{domain_id}
- deleteDisable this return domain/v1/tenants/{tenant_id}/return-domains/{domain_id}New payments can no longer use it as return url, and drivers returning from checkout of earlier payments that did get its error instead of the redirect.
- postCheck public DNS ownership/v1/tenants/{tenant_id}/return-domains/{domain_id}/verifyChecks the TXT record at ivora-return.<hostname for this domain's exact value: dns verified and ready while it matches.