---
title: "Verify the proxy configuration for your domain"
method: POST
path: "/proxy_checks"
tags: ["Proxy Checks"]
---

# Verify the proxy configuration for your domain

`POST /proxy_checks`

This endpoint can be used to validate that a proxy-enabled domain is operational.
It tries to verify that the proxy URL provided in the parameters maps to a functional proxy that can reach the Clerk Frontend API.

You can use this endpoint before you set a proxy URL for a domain. This way you can ensure that switching to proxy-based
configuration will not lead to downtime for your instance.

The `proxy_url` parameter allows for testing proxy configurations for domains that don't have a proxy URL yet, or operate on
a different proxy URL than the one provided. It can also be used to re-validate a domain that is already configured to work with a proxy.

## Request body

- object
  - `domain_id` string — The ID of the domain that will be updated.
  - `proxy_url` string — The full URL of the proxy which will forward requests to the Clerk Frontend API for this domain. e.g. https://example.com/__clerk

## Response `200`

Health check information about a domain's proxy configuration validation attempt.

- ProxyCheck
  - `object` 'proxy_check', required
  - `id` string, required
  - `domain_id` string, required
  - `last_run_at` integer, nullable, required — Unix timestamp of last run.
  - `proxy_url` string, required
  - `successful` boolean, required
  - `created_at` integer, required — Unix timestamp of creation.
  - `updated_at` integer, required — Unix timestamp of last update.

## Other responses

- `400` — Request was not successful
- `422` — Invalid request parameters

---

[API](https://skmtc.net/clerk/apis/clerk-backend-api.md) · [All operations](https://skmtc.net/clerk/apis/clerk-backend-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/clerk/clerk-backend-api/revisions/cf036e7951d3/schema)