Docs / Troubleshooting

Troubleshooting

A guide to understanding API error codes and resolving common issues when managing your domains and DNS records.

Standard HTTP Status Codes

CodeMeaningDescription
200OKRequest processed successfully.
201CreatedResource (Domain/Record) successfully created.
400Bad RequestValidation failed (invalid IP, missing fields).
401UnauthorizedMissing or invalid Bearer Token.
404Not FoundDomain or Record ID does not exist.
409ConflictResource already exists.

Common Error Scenarios

Authentication Failure

Occurs when the Authorization header is missing or contains an expired/invalid token.

{
  "success": false,
  "error": "Unauthorized: Invalid Bearer token"
}
Solution: Generate a new token via the /auth/login endpoint.

Domain Already Exists

Occurs when attempting to register a domain that is already claimed in the system.

{
  "success": false,
  "error": "Domain example.com is already registered by another user"
}
Solution: Contact support if you own the domain but cannot claim it.

DNS Record Already Exists

Occurs when trying to add a duplicate record (same type, name, and content).

{
  "success": false,
  "error": "Record already exists",
  "details": "A record for 'blog' with value '1.2.3.4' already exists."
}
Solution: Use the List Records API to check existing entries before adding.

Invalid DNS Data

Occurs when the input does not match DNS standards (e.g., invalid IP for A record).

{
  "success": false,
  "error": "Validation Error",
  "details": "Invalid IPv4 address provided for type A"
}
Solution: Ensure your value matches the requirements for the selected type.

Domain Not Found

Occurs when performing actions on a domain not associated with your account.

{
  "success": false,
  "error": "Domain not found",
  "message": "Please register the domain before adding records."
}