---
title: "Verify custom domain"
method: POST
path: "/api/apps/{app_id}/custom-domains/{domain_id}/verify"
---

# Verify custom domain

`POST /api/apps/{app_id}/custom-domains/{domain_id}/verify`

<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Asks the hosting provider to check the domain's DNS.

Verification normally starts on its own when you link a domain. Call this when you have just fixed the DNS records and don't want to wait for the next automatic check.

A successful call means the check was accepted, not that the domain is verified. Poll [Get custom domain status](/api-reference/get-custom-domain-status) for the result.

A domain whose DNS doesn't point to Base44 yet fails in a way this endpoint doesn't document. Treat any failure here as "the check didn't start", fix the DNS records, and call this again.

## Path parameters

- `app_id` string, required — ID of the app the domain belongs to.
- `domain_id` string, required — ID of the custom domain. Get this from [List custom domains](/api-reference/list-custom-domains).

## Response `200`

The provider accepted the verification request.

- DomainMessageResponse — A one-line confirmation.
  - `message` string, required — What happened, in plain text.

## Other responses

- `401` — Missing or invalid credentials.
- `403` — You don't have access to this app, or you used a workspace API key. These endpoints take a personal API key.
- `404` — The app has no custom domain with this ID, or the app doesn't exist.

---

[API](https://skmtc.dev/base44/apis/base44-app-management-api.md) · [All operations](https://skmtc.dev/base44/apis/base44-app-management-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/base44/base44-app-management-api/revisions/173e4e9c63c2/schema)