1ms.tools
APIs

Domain Setup Checker API

Integrate DNS and HTTP reachability checks into domain launch workflows to diagnose resolution and website access.

1 credit per successful task10 external calls / minute / account
Get an API keyTry the online toolAPI docs

Integration use cases

Use it for custom domain onboarding, pre-launch checks and customer support. Add DNS and website reachability results to help users locate resolution targets and access problems.

Request example

Replace the example key with one created in your console. The input demonstrates integration; consult the API documentation for all fields and validation rules.

POST /openapi/tools/domain-setup-checker/execute
curl 'https://1ms.tools/openapi/tools/domain-setup-checker/execute' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: YOUR_UNIQUE_REQUEST_ID' \
  -d '{"domain":"example.com"}'
Asynchronous response and result retrieval

An accepted request returns HTTP 202 and job metadata. The job has not completed yet; this example shows commonly used fields.

{
  "code": 0,
  "message": "ok",
  "data": {
    "id": "JOB_ID",
    "status": "queued",
    "result": null,
    "creditCost": 1,
    "pollAfterMs": 6000,
    "statusUrl": "/openapi/jobs/JOB_ID"
  }
}

Wait at least six seconds before polling with the same key. Read result on succeeded, or error on failed or canceled.

curl 'https://1ms.tools/openapi/jobs/JOB_ID' \
  -H 'Authorization: Bearer YOUR_API_KEY'

Results reflect the current query path; networks and caches in other locations may observe different behavior.

API integration questions

Use Authorization: Bearer YOUR_API_KEY or X-API-Key. External endpoints require a valid key; browser cookies cannot replace it. Keep keys on a server or in a trusted application environment.

Creating a job reserves 1 credit, finalized on success. Invalid input or insufficient credits creates no job; failure, timeout or cancellation of a queued job refunds the reservation. Polling costs no credits but counts toward the rate limit.

This endpoint uses asynchronous jobs, returning HTTP 202 and a job ID first. Poll the returned statusUrl and read result on success. Use Idempotency-Key for submission retries.

Each account can make 10 external business requests per calendar minute, shared by all keys and counted separately from web requests. Polling, uploads and execution all count; respect Retry-After on HTTP 429.